From 73a95f72d3faf019147a304fd657e1540bababe2 Mon Sep 17 00:00:00 2001
From: Paula <paula.mihu@arangodb.com>
Date: Thu, 27 Nov 2025 13:27:24 +0100
Subject: [PATCH 1/2] better description for endpoints URLs

---
 site/content/ai-suite/graph-analytics.md | 296 +++++++++++++++++++----
 1 file changed, 254 insertions(+), 42 deletions(-)

diff --git a/site/content/ai-suite/graph-analytics.md b/site/content/ai-suite/graph-analytics.md
index 9a885d2b0e..774a268a68 100644
--- a/site/content/ai-suite/graph-analytics.md
+++ b/site/content/ai-suite/graph-analytics.md
@@ -135,6 +135,12 @@ The interface for managing the engines depends on the environment you use:
 
 {{< tag "AI Data Platform" >}}
 
+{{< info >}}
+This section covers managing Graph Analytics Engines on the **AI Data Platform**.
+
+If you're using **Arango Managed Platform (AMP)**, skip to the [Management API](#management-api) section instead.
+{{< /info >}}
+
 GAEs are deployed and deleted via the [AI orchestration service](reference/ai-orchestrator.md)
 in the AI Data Platform.
 
@@ -143,47 +149,86 @@ if the Platform deployment uses a self-signed certificate (default).
 
 #### Start a `graphanalytics` service
 
-`POST <ENGINE_URL>/ai/v1/graphanalytics`
+`POST https://<EXTERNAL_ENDPOINT>:8529/ai/v1/graphanalytics`
 
-Start a GAE via the AI service with an empty request body:
+Start a GAE via the AI service with an empty request body. This returns a **SERVICE_ID** that you will need to construct the Engine API URL in the next section.
 
 ```sh
-# Example with a JWT session token
-ADB_TOKEN=$(curl -sSk -d '{"username":"root", "password": ""}' -X POST https://127.0.0.1:8529/_open/auth | jq -r .jwt)
+# Set your AI Data Platform endpoint
+EXTERNAL_ENDPOINT="<your-endpoint>"  # Example: ai-data-platform.arango.com:8529
 
-Service=$(curl -sSk -H "Authorization: bearer $ADB_TOKEN" -X POST https://127.0.0.1:8529/ai/v1/graphanalytics)
+# Get an authentication token (example with JWT session token)
+ADB_TOKEN=$(curl -sSk -X POST \
+  -d '{"username":"root","password":""}' \
+  "https://$EXTERNAL_ENDPOINT/_open/auth" | jq -r .jwt)
+
+# Start the Graph Analytics service
+Service=$(curl -sSk -H "Authorization: bearer $ADB_TOKEN" \
+  -X POST "https://$EXTERNAL_ENDPOINT/ai/v1/graphanalytics")
+
+# Extract the service ID (needed for Engine API URL construction)
 ServiceID=$(echo "$Service" | jq -r ".serviceInfo.serviceId")
+
 if [[ "$ServiceID" == "null" ]]; then 
-  echo "Error starting gral engine"
+  echo "Error starting Graph Analytics Engine"
 else
-  echo "Engine started successfully"
+  echo "Graph Analytics service started successfully"
+  echo "Service ID: $ServiceID"
+  echo "Save this Service ID for constructing the Engine API URL"
 fi
+
 echo "$Service" | jq
 ```
 
+**Example response:**
+```json
+{
+  "serviceInfo": {
+    "serviceId": "tqcge",
+    "description": "Install complete",
+    "status": "DEPLOYED",
+    "namespace": "arangodb"
+  }
+}
+```
+
+{{< info >}}
+Save the `serviceId` from the response. You will use it to construct the Engine API URL for running graph analytics operations.
+{{< /info >}}
+
 #### List the services
 
-`POST <ENGINE_URL>/ai/v1/list_services`
+`POST https://<EXTERNAL_ENDPOINT>:8529/ai/v1/list_services`
 
 You can list all running services managed by the AI service, including the
 `graphanalytics` services:
 
 ```sh
-curl -sSk -H "Authorization: bearer $ADB_TOKEN" -X POST https://127.0.0.1:8529/ai/v1/list_services | jq
+curl -sSk -H "Authorization: bearer $ADB_TOKEN" \
+  -X POST "https://$EXTERNAL_ENDPOINT/ai/v1/list_services" | jq
 ```
 
 #### Stop a `graphanalytics` service
 
+`DELETE https://<EXTERNAL_ENDPOINT>:8529/ai/v1/service/<SERVICE_ID>`
+
 Delete the desired engine via the AI service using the service ID:
 
 ```sh
-curl -sSk -H "Authorization: bearer $ADB_TOKEN" -X DELETE https://127.0.0.1:8529/ai/v1/service/$ServiceID | jq
+curl -sSk -H "Authorization: bearer $ADB_TOKEN" \
+  -X DELETE "https://$EXTERNAL_ENDPOINT/ai/v1/service/$ServiceID" | jq
 ```
 
 ### Management API
 
 {{< tag "AMP" >}}
 
+{{< info >}}
+This section covers managing Graph Analytics Engines on the **Arango Managed Platform (AMP)**.
+
+If you are using the **AI Data Platform**, use the [AI service](#ai-service) instead.
+{{< /info >}}
+
 GAEs are deployed and deleted with the Management API for graph analytics on the
 Arango Managed Platform (AMP). You can also list the available engine sizes and
 get information about deployed engines.
@@ -304,76 +349,182 @@ curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -X DELETE "$BASE_URL/engines
 
 ## Engine API
 
-### Determine the engine URL
+{{< info >}}
+Regardless of which platform you used to start your Graph Analytics Engine:
+- **AI Data Platform**: You have a **SERVICE_ID** from the AI service,
+- **Arango Managed Platform (AMP)**: You have an **ENGINE_ID** from the Management API,
+
+Both platforms use the **same Engine API** for graph analytics operations, but with different URL structures.
+{{< /info >}}
+
+### Determine the Engine API URL
+
+The Engine API URL is constructed from multiple parts depending on your platform.
 
 {{< tabs "platforms" >}}
 
 {{< tab "AI Data Platform" >}}
-To determine the base URL of the engine API, use the base URL of the Platform
-deployment and append `/gral/<SERVICE_ID>`, e.g.
-`https://127.0.0.1:8529/gral/arangodb-gral-tqcge`.
 
-The service ID is returned by the call to the AI service for
-[starting the `graphanalytics` service](#start-a-graphanalytics-service).
-You can also list the service IDs like so:
+**URL Pattern:**
+
+```
+https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/<operation>
+```
+
+Where:
+- `<EXTERNAL_ENDPOINT>`: Your AI Data Platform endpoint with port (e.g., `ai-data-platform.arango.com:8529`)
+- `<SERVICE_ID>`: From the [AI service response](#start-a-graphanalytics-service) when you started the service
+- `<operation>`: The operation or algorithm you want to perform (e.g., `loaddata`, `pagerank`, `storeresults`)
+
+**Example:**
+
+```
+https://ai-data-platform.arango.com:8529/gral/tqcge/v1/pagerank
+```
+
+**Getting the SERVICE_ID:**
+
+The service ID is returned when you [start the Graph Analytics service](#start-a-graphanalytics-service). 
+
+You can also list all service IDs using kubectl:
 
 ```sh
 kubectl -n arangodb get svc arangodb-gral -o jsonpath="{.spec.selector.release}"
 ```
 
-Store the base URL in a variable called `ENGINE_URL`:
+For convenience, you can store the Engine API base URL in a variable:
 
 ```bash
-ENGINE_URL='https://...'
+# Your Platform endpoint with port
+EXTERNAL_ENDPOINT="ai-data-platform.arango.com:8529"
+
+# Service ID from when you started the service
+SERVICE_ID="tqcge"
+
+# Construct the Engine API base URL
+ENGINE_URL="https://$EXTERNAL_ENDPOINT/gral/$SERVICE_ID"
 ```
 
-To authenticate requests, you need to use a bearer token in HTTP header:
+This makes subsequent requests shorter and easier to manage. Alternatively, you can use the full URL directly in each request.
+
+**Verify the connection:**
+
+```bash
+curl -sSk -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
 ```
-Authorization: bearer <TOKEN>
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+**URL Pattern:**
+
+```
+https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/<operation>
 ```
 
-You can save the token in a variable to ease scripting. Note that this should be
-the token string only and not include quote marks. The following examples assume
-Bash as the shell and that the `curl` and `jq` commands are available.
+Where:
+- `<APPLICATION_ENDPOINT>`: The endpoint of your deployment holding the graph data you want to analyze 
+- `<ENGINE_ID>`: From the [Management API response](#deploy-an-engine) when you deployed the engine
+- `<operation>`: The operation or algorithm you want to perform (e.g., `loaddata`, `pagerank`, `storeresults`)
 
-An example of authenticating a request using cURL and a session token:
+**How to construct the Engine URL:**
+
+1. In the AMP dashboard, copy the **APPLICATION ENDPOINT** of your deployment (e.g., `123456abcdef.arangodb.cloud`).
+2. Use port `:8829` for the Engine API.
+3. Add the path: `/graph-analytics/engines/<ENGINE_ID>/v1/<operation>`
+
+**Getting the ENGINE_ID:**
+
+The engine ID is returned when you [deploy an engine](#deploy-an-engine).
+
+If you can't remember the engine ID, you can [list all engines](#list-all-engines).
+
+**Example:**
+
+```
+https://123456abcdef.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/pagerank
+```
+For convenience, you can store the Engine API base URL in a variable:
 
 ```bash
-PLATFORM_BASEURL="https://127.0.0.1:8529"
+# Your AMP deployment endpoint (without port)
+APPLICATION_ENDPOINT="123456abcdef.arangodb.cloud"
 
-ADB_TOKEN=$(curl -X POST -d "{\"username\":\"<ADB_USER>\",\"password\":\"<ADB_PASS>\"}" "$PLATFORM_BASEURL/_open/auth" | jq -r '.jwt')
+# Engine ID from when you deployed the engine
+ENGINE_ID="zYxWvU9876"
 
-curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
+# Construct the Engine API base URL
+ENGINE_URL="https://$APPLICATION_ENDPOINT:8829/graph-analytics/engines/$ENGINE_ID"
 ```
-{{< /tab >}}
 
-{{< tab "Arango Managed Platform (AMP)" >}}
-To determine the base URL of the engine API, use the AMP dashboard
-and copy the __APPLICATION ENDPOINT__ of the deployment that holds the graph data
-you want to analyze. Replace the port with `8829` and append
-`/graph-analytics/engines/<ENGINE_ID>`, e.g.
-`https://<123456abcdef>.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876`.
-If you can't remember the engine ID, you can [List all engines](#list-all-engines).
+This makes subsequent requests shorter and easier to manage. Alternatively, you can use the full URL directly in each request.
 
-Store the base URL in a variable called `ENGINE_URL`:
+**Verify the connection:**
 
 ```bash
-ENGINE_URL='https://...'
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$ENGINE_URL/v1/jobs"
 ```
 
-To authenticate requests, you need to use a bearer token in HTTP header:
+{{< /tab >}}
+
+{{< /tabs >}}
+
+{{< tip >}}
+Both platforms use the same Engine API operations and algorithms (`/v1/loaddata`, `/v1/pagerank`, etc.), but you reach them through different URL structures.
+{{< /tip >}}
+
+{{< info >}}
+For brevity, the endpoint examples use `<ENGINE_URL>` as a placeholder. You can either:
+- Set it as a variable (recommended for multiple requests) as shown above, or
+- Replace it with the full URL for your platform in each request.
+{{< /info >}}
+
+### Authentication
+
+Authenticate Engine API requests using a bearer token in the HTTP header:
+
 ```
 Authorization: bearer <TOKEN>
 ```
 
-- If __Auto login to database UI__ is enabled for the AMP deployment,
-  this can be the same access token as used for the management API.
-- If it is disabled, use an ArangoDB session token (JWT user token) instead.
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
 
 You can save the token in a variable to ease scripting. Note that this should be
 the token string only and not include quote marks. The following examples assume
 Bash as the shell and that the `curl` and `jq` commands are available.
 
+**Example with JWT session token:**
+
+```bash
+# Platform endpoint (from previous section)
+EXTERNAL_ENDPOINT="ai-data-platform.arango.com:8529"
+
+# Get authentication token
+ADB_TOKEN=$(curl -sSk -X POST \
+  -d '{"username":"<ADB_USER>","password":"<ADB_PASS>"}' \
+  "https://$EXTERNAL_ENDPOINT/_open/auth" | jq -r '.jwt')
+
+# Use in requests
+curl -sSk -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+The authentication method depends on the [**Auto login to database UI**](../amp/deployments/_index.md#auto-login-to-database-ui) setting:
+
+- If **Auto login to database UI** is enabled for the AMP deployment, this can
+  be the same access token as used for the management API.
+- If it is disabled, use an ArangoDB session token (JWT user token) instead.
+
+You can save the token in a variable to ease scripting. Note that this should
+be the token string only and not include quote marks. The following examples
+assume Bash as the shell and that the `curl` and `jq` commands are available.
+
 An example of authenticating a request using cURL and a session token:
 
 ```bash
@@ -383,6 +534,7 @@ ADB_TOKEN=$(curl -X POST -d "{\"username\":\"<ADB_USER>\",\"password\":\"<ADB_PA
 
 curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
 ```
+
 {{< /tab >}}
 
 {{< /tabs >}}
@@ -400,6 +552,10 @@ Request and response payloads are JSON-encoded in the engine API.
 
 `POST <ENGINE_URL>/v1/loaddata`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/loaddata`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/loaddata`
+
 Import graph data from a database of the ArangoDB deployment. You can import
 named graphs as well as sets of node and edge collections (see
 [Managed and unmanaged graphs](../arangodb/3.12/graphs/_index.md#managed-and-unmanaged-graphs)).
@@ -414,6 +570,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d '{"database":"_system","gra
 
 `POST <ENGINE_URL>/v1/pagerank`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/pagerank`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/pagerank`
+
 PageRank is a well known algorithm to rank nodes in a graph: the more
 important a node, the higher rank it gets. It goes back to L. Page and S. Brin's
 [paper](http://infolab.stanford.edu/pub/papers/google.pdf) and
@@ -481,6 +641,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 `POST <ENGINE_URL>/v1/wcc`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/wcc`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/wcc`
+
 The weakly connected component algorithm partitions a graph into maximal groups
 of nodes, so that within a group, all nodes are reachable from each node
 by following the edges, ignoring their direction.
@@ -505,6 +669,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}"
 
 `POST <ENGINE_URL>/v1/scc`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/scc`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/scc`
+
 The strongly connected components algorithm partitions a graph into maximal
 groups of nodes, so that within a group, all nodes are reachable from each
 node by following the edges in their direction.
@@ -546,6 +714,10 @@ available, which should be equally usable for most use cases.
 
 `POST <ENGINE_URL>/v1/betweennesscentrality`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/betweennesscentrality`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/betweennesscentrality`
+
 A relatively expensive algorithm with complexity `O(V*E)` where `V` is the
 number of nodes and `E` is the number of edges in the graph.
 
@@ -606,6 +778,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 `POST <ENGINE_URL>/v1/linerank`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/linerank`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/linerank`
+
 Another common measure is the [*betweenness* centrality](https://en.wikipedia.org/wiki/Betweenness_centrality):
 It measures the number of times a node is part of shortest paths between any
 pairs of nodes. For a node *v* betweenness is defined as:
@@ -652,6 +828,10 @@ based on common location, interests, occupation, etc.
 
 `POST <ENGINE_URL>/v1/labelpropagation`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/labelpropagation`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/labelpropagation`
+
 [*Label Propagation*](https://arxiv.org/pdf/0709.2938) can be used to implement
 community detection on large graphs.
 
@@ -708,6 +888,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 `POST <ENGINE_URL>/v1/attributepropagation`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/attributepropagation`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/attributepropagation`
+
 The attribute propagation algorithm can be used to implement community detection.
 It works similar to the label propagation algorithm, but every node additionally
 accumulates a memory of observed labels instead of forgetting all but one label.
@@ -783,6 +967,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 `POST <ENGINE_URL>/v1/storeresults`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/storeresults`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/storeresults`
+
 You need to specify to which ArangoDB `database` and `target_collection` to save
 the results to. They need to exist already.
 
@@ -813,6 +1001,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -X POST -d "{\"database\":\"_system\"
 
 `GET <ENGINE_URL>/v1/jobs`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs`
+
 List all active and finished jobs.
 
 ```bash
@@ -823,6 +1015,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
 
 `GET <ENGINE_URL>/v1/jobs/<JOB_ID>`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs/<JOB_ID>`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs/<JOB_ID>`
+
 Get detailed information about a specific job.
 
 ```bash
@@ -834,6 +1030,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs/$JOB_ID"
 
 `DELETE <ENGINE_URL>/v1/jobs/<JOB_ID>`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs/<JOB_ID>`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs/<JOB_ID>`
+
 Delete a specific job.
 
 ```bash
@@ -845,6 +1045,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" -X DELETE "$ENGINE_URL/v1/jobs/$JOB_I
 
 `GET <ENGINE_URL>/v1/graphs`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs`
+
 List all loaded sets of graph data that reside in the memory of the engine node.
 
 ```bash
@@ -855,6 +1059,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/graphs"
 
 `GET <ENGINE_URL>/v1/graphs/<GRAPH_ID>`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs/<GRAPH_ID>`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs/<GRAPH_ID>`
+
 Get detailed information about a specific set of graph data.
 
 ```bash
@@ -866,6 +1074,10 @@ curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/graphs/$GRAPH_ID"
 
 `DELETE <ENGINE_URL>/v1/graphs/<GRAPH_ID>`
 
+**Examples:**
+- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs/<GRAPH_ID>`
+- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs/<GRAPH_ID>`
+
 Delete a specific set of graph data, removing it from the memory of the engine node.
 
 ```bash

From 445eea589914fdabc09e128d27160b42ecc4bb88 Mon Sep 17 00:00:00 2001
From: Paula <paula.mihu@arangodb.com>
Date: Wed, 10 Dec 2025 15:52:34 +0100
Subject: [PATCH 2/2] Updated endpoint URLs and examples for clarity and
 structure; separated platforms

---
 site/content/ai-suite/graph-analytics.md | 757 +++++++++++++++++------
 1 file changed, 556 insertions(+), 201 deletions(-)

diff --git a/site/content/ai-suite/graph-analytics.md b/site/content/ai-suite/graph-analytics.md
index 774a268a68..92bcac6df2 100644
--- a/site/content/ai-suite/graph-analytics.md
+++ b/site/content/ai-suite/graph-analytics.md
@@ -124,6 +124,12 @@ setting in AMP:
 
 {{< /tabs >}}
 
+{{< info >}}
+Note that all cURL examples use placeholder values that you should replace with your actual values:
+- **AI Data Platform**: `ai-data-platform.arango.com` (platform endpoint), `tqcge` (service ID).
+- **AMP**: `a1b2c3d4e5f6.arangodb.cloud` (deployment endpoint), `zYxWvU9876` (engine ID).
+{{< /info >}}
+
 ## Start and stop Graph Analytics Engines
 
 The interface for managing the engines depends on the environment you use:
@@ -149,22 +155,24 @@ if the Platform deployment uses a self-signed certificate (default).
 
 #### Start a `graphanalytics` service
 
-`POST https://<EXTERNAL_ENDPOINT>:8529/ai/v1/graphanalytics`
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/ai/v1/graphanalytics
+```
 
 Start a GAE via the AI service with an empty request body. This returns a **SERVICE_ID** that you will need to construct the Engine API URL in the next section.
 
 ```sh
 # Set your AI Data Platform endpoint
-EXTERNAL_ENDPOINT="<your-endpoint>"  # Example: ai-data-platform.arango.com:8529
+EXTERNAL_ENDPOINT="<your-endpoint>"  # Example: ai-data-platform.arango.com
 
 # Get an authentication token (example with JWT session token)
 ADB_TOKEN=$(curl -sSk -X POST \
   -d '{"username":"root","password":""}' \
-  "https://$EXTERNAL_ENDPOINT/_open/auth" | jq -r .jwt)
+  "https://$EXTERNAL_ENDPOINT:8529/_open/auth" | jq -r .jwt)
 
 # Start the Graph Analytics service
 Service=$(curl -sSk -H "Authorization: bearer $ADB_TOKEN" \
-  -X POST "https://$EXTERNAL_ENDPOINT/ai/v1/graphanalytics")
+  -X POST "https://$EXTERNAL_ENDPOINT:8529/ai/v1/graphanalytics")
 
 # Extract the service ID (needed for Engine API URL construction)
 ServiceID=$(echo "$Service" | jq -r ".serviceInfo.serviceId")
@@ -198,25 +206,29 @@ Save the `serviceId` from the response. You will use it to construct the Engine
 
 #### List the services
 
-`POST https://<EXTERNAL_ENDPOINT>:8529/ai/v1/list_services`
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/ai/v1/list_services
+```
 
 You can list all running services managed by the AI service, including the
 `graphanalytics` services:
 
 ```sh
-curl -sSk -H "Authorization: bearer $ADB_TOKEN" \
-  -X POST "https://$EXTERNAL_ENDPOINT/ai/v1/list_services" | jq
+curl -sSk -H "Authorization: bearer <ADB_TOKEN>" \
+  -X POST "https://ai-data-platform.arango.com:8529/ai/v1/list_services" | jq
 ```
 
 #### Stop a `graphanalytics` service
 
-`DELETE https://<EXTERNAL_ENDPOINT>:8529/ai/v1/service/<SERVICE_ID>`
+```
+DELETE https://<EXTERNAL_ENDPOINT>:8529/ai/v1/service/<SERVICE_ID>
+```
 
 Delete the desired engine via the AI service using the service ID:
 
 ```sh
-curl -sSk -H "Authorization: bearer $ADB_TOKEN" \
-  -X DELETE "https://$EXTERNAL_ENDPOINT/ai/v1/service/$ServiceID" | jq
+curl -sSk -H "Authorization: bearer <ADB_TOKEN>" \
+  -X DELETE "https://ai-data-platform.arango.com:8529/ai/v1/service/tqcge" | jq
 ```
 
 ### Management API
@@ -233,25 +245,25 @@ GAEs are deployed and deleted with the Management API for graph analytics on the
 Arango Managed Platform (AMP). You can also list the available engine sizes and
 get information about deployed engines.
 
-To determine the base URL of the management API, use the AMP dashboard
-and copy the __APPLICATION ENDPOINT__ of the deployment that holds the graph data
-you want to analyze. Replace the port with `8829` and append
-`/graph-analytics/api/graphanalytics/v1`, e.g.
-`https://123456abcdef.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1`.
-
-Store the base URL in a variable called `BASE_URL`:
+**Management API URL structure:**
 
-```bash
-BASE_URL='https://...'
 ```
+https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/
+```
+
+Where:
+- `<APPLICATION_ENDPOINT>` is your deployment endpoint from the AMP dashboard (e.g., `a1b2c3d4e5f6.arangodb.cloud`)
+- Port is always `:8829` for the Management API
+
+**Authentication:**
 
-To authenticate requests, you need to use the following HTTP header:
+All requests require an AMP access token in the Authorization header:
 
 ```
 Authorization: bearer <ARANGO_GRAPH_TOKEN>
 ```
 
-You can create an AMP access token with `oasisctl login`. Save it in a
+You can create an AMP access token with [`oasisctl login`](../amp/oasisctl/login.md). Save it in a
 variable to ease scripting. Note that this should be the token string only and
 not include quote marks. The following examples assume Bash as the shell and
 that the `curl` and `jq` commands are available.
@@ -263,46 +275,58 @@ ARANGO_GRAPH_TOKEN="$(oasisctl login --key-id "<AG_KEY_ID>" --key-secret "<AG_KE
 Example with cURL that uses the token variable:
 
 ```bash
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$BASE_URL/api-version"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/api-version"
 ```
 
 Request and response payloads are JSON-encoded in the management API.
 
 #### Get the API version
 
-`GET <BASE_URL>/api-version`
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/api-version
+```
 
-Retrieve the version information of the management API.
+Example to retrieve the version information of the Management API:
 
 ```bash
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$BASE_URL/api-version"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/api-version"
 ```
 
 #### List engine sizes
 
-`GET <BASE_URL>/enginesizes`
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/enginesizes
+```
 
 List the available engine sizes, which is a combination of the number of cores
 and the size of the RAM, starting at 1 CPU and 4 GiB of memory (`e4`).
 
 ```bash
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$BASE_URL/enginesizes"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/enginesizes"
 ```
 
 #### List engine types
 
-`GET <BASE_URL>/enginetypes`
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/enginetypes
+```
 
 List the available engine types. The only type supported for GAE workloads is
 called `gral`.
 
 ```bash
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$BASE_URL/enginetypes"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/enginetypes"
 ```
 
 #### Deploy an engine
 
-`POST <BASE_URL>/engines`
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/engines
+```
 
 Set up a GAE adjacent to the AMP deployment, for example, using an
 engine size of `e4`.
@@ -310,54 +334,57 @@ engine size of `e4`.
 The engine ID is returned in the `id` attribute.
 
 ```bash
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -X POST -d '{"type_id":"gral","size_id":"e4"}' "$BASE_URL/engines"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  -X POST \
+  -d '{"type_id":"gral","size_id":"e4"}' \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/engines"
 ```
 
 #### List all engines
 
-`GET <BASE_URL>/engines`
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/engines
+```
 
 List all deployed GAEs of a AMP deployment.
 
 The engine IDs are in the `id` attributes.
 
 ```bash
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$BASE_URL/engines"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/engines"
 ```
 
 #### Get an engine
 
-`GET <BASE_URL>/engines/<ENGINE_ID>`
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/engines/<ENGINE_ID>
+```
 
 List the detailed information about a specific GAE.
 
 ```bash
-ENGINE_ID="zYxWvU9876"
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "$BASE_URL/engines/$ENGINE_ID"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/engines/zYxWvU9876"
 ```
 
 #### Delete an engine
 
-`DELETE <BASE_URL>/engines/<ENGINE_ID>`
+```
+DELETE https://<APPLICATION_ENDPOINT>:8829/graph-analytics/api/graphanalytics/v1/engines/<ENGINE_ID>
+```
 
 Delete a no longer needed GAE, freeing any data it holds in memory.
 
 ```bash
-ENGINE_ID="zYxWvU9876"
-curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -X DELETE "$BASE_URL/engines/$ENGINE_ID"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" \
+  -X DELETE \
+  "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/api/graphanalytics/v1/engines/zYxWvU9876"
 ```
 
 ## Engine API
 
-{{< info >}}
-Regardless of which platform you used to start your Graph Analytics Engine:
-- **AI Data Platform**: You have a **SERVICE_ID** from the AI service,
-- **Arango Managed Platform (AMP)**: You have an **ENGINE_ID** from the Management API,
-
-Both platforms use the **same Engine API** for graph analytics operations, but with different URL structures.
-{{< /info >}}
-
-### Determine the Engine API URL
+The Engine API lets you load data, run algorithms, and manage results. Both platforms use the same API endpoints but with different URL structures.
 
 The Engine API URL is constructed from multiple parts depending on your platform.
 
@@ -365,16 +392,13 @@ The Engine API URL is constructed from multiple parts depending on your platform
 
 {{< tab "AI Data Platform" >}}
 
-**URL Pattern:**
-
 ```
-https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/<operation>
+https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/
 ```
 
 Where:
-- `<EXTERNAL_ENDPOINT>`: Your AI Data Platform endpoint with port (e.g., `ai-data-platform.arango.com:8529`)
+- `<EXTERNAL_ENDPOINT>`: Your AI Data Platform endpoint (e.g., `ai-data-platform.arango.com`)
 - `<SERVICE_ID>`: From the [AI service response](#start-a-graphanalytics-service) when you started the service
-- `<operation>`: The operation or algorithm you want to perform (e.g., `loaddata`, `pagerank`, `storeresults`)
 
 **Example:**
 
@@ -382,9 +406,7 @@ Where:
 https://ai-data-platform.arango.com:8529/gral/tqcge/v1/pagerank
 ```
 
-**Getting the SERVICE_ID:**
-
-The service ID is returned when you [start the Graph Analytics service](#start-a-graphanalytics-service). 
+The port `:8529` is added when constructing URLs.
 
 You can also list all service IDs using kubectl:
 
@@ -395,14 +417,14 @@ kubectl -n arangodb get svc arangodb-gral -o jsonpath="{.spec.selector.release}"
 For convenience, you can store the Engine API base URL in a variable:
 
 ```bash
-# Your Platform endpoint with port
-EXTERNAL_ENDPOINT="ai-data-platform.arango.com:8529"
+# Your Platform endpoint (without port)
+EXTERNAL_ENDPOINT="ai-data-platform.arango.com"
 
 # Service ID from when you started the service
 SERVICE_ID="tqcge"
 
 # Construct the Engine API base URL
-ENGINE_URL="https://$EXTERNAL_ENDPOINT/gral/$SERVICE_ID"
+ENGINE_URL="https://$EXTERNAL_ENDPOINT:8529/gral/$SERVICE_ID"
 ```
 
 This makes subsequent requests shorter and easier to manage. Alternatively, you can use the full URL directly in each request.
@@ -417,28 +439,13 @@ curl -sSk -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
 
 {{< tab "Arango Managed Platform (AMP)" >}}
 
-**URL Pattern:**
-
 ```
-https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/<operation>
+https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/
 ```
 
 Where:
 - `<APPLICATION_ENDPOINT>`: The endpoint of your deployment holding the graph data you want to analyze 
-- `<ENGINE_ID>`: From the [Management API response](#deploy-an-engine) when you deployed the engine
-- `<operation>`: The operation or algorithm you want to perform (e.g., `loaddata`, `pagerank`, `storeresults`)
-
-**How to construct the Engine URL:**
-
-1. In the AMP dashboard, copy the **APPLICATION ENDPOINT** of your deployment (e.g., `123456abcdef.arangodb.cloud`).
-2. Use port `:8829` for the Engine API.
-3. Add the path: `/graph-analytics/engines/<ENGINE_ID>/v1/<operation>`
-
-**Getting the ENGINE_ID:**
-
-The engine ID is returned when you [deploy an engine](#deploy-an-engine).
-
-If you can't remember the engine ID, you can [list all engines](#list-all-engines).
+- `<ENGINE_ID>`: From the [Management API response](#deploy-an-engine) when you deployed the engine. If you can't remember the engine ID, you can [list all engines](#list-all-engines).
 
 **Example:**
 
@@ -475,7 +482,7 @@ Both platforms use the same Engine API operations and algorithms (`/v1/loaddata`
 {{< /tip >}}
 
 {{< info >}}
-For brevity, the endpoint examples use `<ENGINE_URL>` as a placeholder. You can either:
+For brevity, the above examples use `<ENGINE_URL>` as a placeholder. You can either:
 - Set it as a variable (recommended for multiple requests) as shown above, or
 - Replace it with the full URL for your platform in each request.
 {{< /info >}}
@@ -500,15 +507,18 @@ Bash as the shell and that the `curl` and `jq` commands are available.
 
 ```bash
 # Platform endpoint (from previous section)
-EXTERNAL_ENDPOINT="ai-data-platform.arango.com:8529"
+EXTERNAL_ENDPOINT="ai-data-platform.arango.com"
+
+# Service ID from when you started the service
+SERVICE_ID="tqcge"
 
 # Get authentication token
 ADB_TOKEN=$(curl -sSk -X POST \
   -d '{"username":"<ADB_USER>","password":"<ADB_PASS>"}' \
-  "https://$EXTERNAL_ENDPOINT/_open/auth" | jq -r '.jwt')
+  "https://$EXTERNAL_ENDPOINT:8529/_open/auth" | jq -r '.jwt')
 
-# Use in requests
-curl -sSk -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
+# Example: Use token to verify connection
+curl -sSk -H "Authorization: bearer $ADB_TOKEN" "https://$EXTERNAL_ENDPOINT:8529/gral/$SERVICE_ID/v1/jobs"
 ```
 
 {{< /tab >}}
@@ -528,11 +538,15 @@ assume Bash as the shell and that the `curl` and `jq` commands are available.
 An example of authenticating a request using cURL and a session token:
 
 ```bash
-APPLICATION_ENDPOINT="https://123456abcdef.arangodb.cloud:8529"
+APPLICATION_ENDPOINT="123456abcdef.arangodb.cloud"
 
-ADB_TOKEN=$(curl -X POST -d "{\"username\":\"<ADB_USER>\",\"password\":\"<ADB_PASS>\"}" "$APPLICATION_ENDPOINT/_open/auth" | jq -r '.jwt')
+# Engine ID from when you deployed the engine
+ENGINE_ID="zYxWvU9876"
+
+ARANGO_GRAPH_TOKEN=$(curl -X POST -d "{\"username\":\"<ADB_USER>\",\"password\":\"<ADB_PASS>\"}" "https://$APPLICATION_ENDPOINT:8529/_open/auth" | jq -r '.jwt')
 
-curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
+# Example: Use token to verify connection
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "https://$APPLICATION_ENDPOINT:8829/graph-analytics/engines/$ENGINE_ID/v1/jobs"
 ```
 
 {{< /tab >}}
@@ -550,29 +564,78 @@ Request and response payloads are JSON-encoded in the engine API.
 
 ### Load data
 
-`POST <ENGINE_URL>/v1/loaddata`
-
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/loaddata`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/loaddata`
-
 Import graph data from a database of the ArangoDB deployment. You can import
 named graphs as well as sets of node and edge collections (see
 [Managed and unmanaged graphs](../arangodb/3.12/graphs/_index.md#managed-and-unmanaged-graphs)).
 
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/loaddata
+```
+
+**Example:**
 ```bash
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d '{"database":"_system","graph_name":"connectedComponentsGraph"}' "$ENGINE_URL/v1/loaddata"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d '{"database":"_system","graph_name":"connectedComponentsGraph"}' "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/loaddata"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
 ```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/loaddata
+```
+
+**Example:**
+
+```bash
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d '{"database":"_system","graph_name":"connectedComponentsGraph"}' "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/loaddata"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
+
 
 ### Run algorithms
 
 #### PageRank
 
-`POST <ENGINE_URL>/v1/pagerank`
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/pagerank`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/pagerank`
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/pagerank
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"damping_factor\":0.85,\"maximum_supersteps\":500,\"seeding_attribute\":\"seed_attr\"}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/pagerank"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/pagerank
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"damping_factor\":0.85,\"maximum_supersteps\":500,\"seeding_attribute\":\"seed_attr\"}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/pagerank"
+```
+{{< /tab >}}
+
+{{< /tabs >}}
 
 PageRank is a well known algorithm to rank nodes in a graph: the more
 important a node, the higher rank it gets. It goes back to L. Page and S. Brin's
@@ -607,12 +670,7 @@ Parameters:
 - `maximum_supersteps`
 - `seeding_attribute` (optional, for seeded PageRank)
 
-Result: the rank of each node
-
-```bash
-GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"damping_factor\":0.85,\"maximum_supersteps\":500,\"seeding_attribute\":\"seed_attr\"}" "$ENGINE_URL/v1/pagerank"
-```
+The result is the rank of each node.
 
 {{< comment >}} Not merged yet
 #### Single-Source Shortest Path (SSSP)
@@ -629,7 +687,7 @@ Parameters:
 - `source_vertex`: The document ID of the source node.
 - `undirected`: Determines whether the algorithm respects the direction of edges.
 
-Result: the distance of each node to the `source_vertex`
+The result is the distance of each node to the `source_vertex`.
 
 ```bash
 GRAPH_ID="234"
@@ -639,11 +697,39 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 #### Weakly Connected Components (WCC)
 
-`POST <ENGINE_URL>/v1/wcc`
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/wcc
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/wcc"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/wcc
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/wcc"
+```
+
+{{< /tab >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/wcc`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/wcc`
+{{< /tabs >}}
 
 The weakly connected component algorithm partitions a graph into maximal groups
 of nodes, so that within a group, all nodes are reachable from each node
@@ -656,22 +742,45 @@ against their direction in a directed graph.
 Parameters:
 - `graph_id`
 
-Result: a component ID for each node. All nodes from the same component
+The result is a component ID for each node. All nodes from the same component
 obtain the same component ID, every two nodes from different components
 obtain different IDs.
 
+#### Strongly Connected Components (SCC)
+
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/scc
+```
+
+**Example:**
+
 ```bash
 GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}" "$ENGINE_URL/v1/wcc"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/scc"
 ```
 
-#### Strongly Connected Components (SCC)
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
 
-`POST <ENGINE_URL>/v1/scc`
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/scc
+```
+
+**Example:**
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/scc`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/scc`
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/scc"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
 
 The strongly connected components algorithm partitions a graph into maximal
 groups of nodes, so that within a group, all nodes are reachable from each
@@ -686,15 +795,10 @@ Parameters:
 
 - `graph_id`
 
-Result: a component ID for each node. All nodes from the same component
+The result is a component ID for each node. All nodes from the same component
 obtain the same component ID, every two nodes from different components
 obtain different IDs.
 
-```bash
-GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID}" "$ENGINE_URL/v1/scc"
-```
-
 #### Vertex Centrality
 
 Centrality measures help identify the most important nodes in a graph.
@@ -712,11 +816,39 @@ available, which should be equally usable for most use cases.
 
 ##### Betweenness Centrality 
 
-`POST <ENGINE_URL>/v1/betweennesscentrality`
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/betweennesscentrality
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"k\":0,\"undirected\":false,\"normalized\":true}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/betweennesscentrality"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/betweennesscentrality
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"k\":0,\"undirected\":false,\"normalized\":true}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/betweennesscentrality"
+```
+
+{{< /tab >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/betweennesscentrality`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/betweennesscentrality`
+{{< /tabs >}}
 
 A relatively expensive algorithm with complexity `O(V*E)` where `V` is the
 number of nodes and `E` is the number of edges in the graph.
@@ -731,12 +863,7 @@ Parameters:
 - `normalized`
 - `parallelism`
 
-Result: a centrality measure for each node
-
-```bash
-GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"k\":0,\"undirected\":false,\"normalized\":true}" "$ENGINE_URL/v1/betweennesscentrality"
-```
+The result is a centrality measure for each node.
 
 {{< comment >}} Not merged yet
 ##### Effective Closeness
@@ -766,7 +893,7 @@ Parameters:
 - `undirected`: Whether to ignore the direction of edges
 - `maximum_supersteps`
 
-Result: a closeness measure for each node
+The result is a closeness measure for each node.
 
 ```bash
 GRAPH_ID="234"
@@ -776,11 +903,39 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 ##### LineRank
 
-`POST <ENGINE_URL>/v1/linerank`
+{{< tabs "platforms" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/linerank`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/linerank`
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/linerank
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"damping_factor\":0.0000001,\"maximum_supersteps\":500}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/linerank"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/linerank
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"damping_factor\":0.0000001,\"maximum_supersteps\":500}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/linerank"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
 
 Another common measure is the [*betweenness* centrality](https://en.wikipedia.org/wiki/Betweenness_centrality):
 It measures the number of times a node is part of shortest paths between any
@@ -808,12 +963,7 @@ Parameters:
 - `damping_factor`
 - `maximum_supersteps`
 
-Result: the line rank of each node
-
-```bash
-GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"damping_factor\":0.0000001,\"maximum_supersteps\":500}" "$ENGINE_URL/v1/linerank"
-```
+The result is the line rank of each node.
 
 #### Community Detection
 
@@ -826,11 +976,39 @@ based on common location, interests, occupation, etc.
 
 ##### Label Propagation
 
-`POST <ENGINE_URL>/v1/labelpropagation`
+{{< tabs "platforms" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/labelpropagation`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/labelpropagation`
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/labelpropagation
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"start_label_attribute\":\"start_attr\",\"synchronous\":false,\"random_tiebreak\":false,\"maximum_supersteps\":500}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/labelpropagation"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/labelpropagation
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"start_label_attribute\":\"start_attr\",\"synchronous\":false,\"random_tiebreak\":false,\"maximum_supersteps\":500}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/labelpropagation"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
 
 [*Label Propagation*](https://arxiv.org/pdf/0709.2938) can be used to implement
 community detection on large graphs.
@@ -877,20 +1055,43 @@ Parameters:
 - `random_tiebreak`
 - `maximum_supersteps`
 
-Result: a community ID for each node
+The result is a community ID for each node.
+
+##### Attribute Propagation
+
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/attributepropagation
+```
+
+**Example:**
 
 ```bash
 GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"start_label_attribute\":\"start_attr\",\"synchronous\":false,\"random_tiebreak\":false,\"maximum_supersteps\":500}" "$ENGINE_URL/v1/labelpropagation"
+curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"start_label_attribute\":\"start_attr\",\"synchronous\":false,\"backwards\":false,\"maximum_supersteps\":500}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/attributepropagation"
 ```
 
-##### Attribute Propagation
+{{< /tab >}}
 
-`POST <ENGINE_URL>/v1/attributepropagation`
+{{< tab "Arango Managed Platform (AMP)" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/attributepropagation`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/attributepropagation`
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/attributepropagation
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"start_label_attribute\":\"start_attr\",\"synchronous\":false,\"backwards\":false,\"maximum_supersteps\":500}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/attributepropagation"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
 
 The attribute propagation algorithm can be used to implement community detection.
 It works similar to the label propagation algorithm, but every node additionally
@@ -924,12 +1125,7 @@ Parameters:
   opposite direction (`true`).
 - `maximum_supersteps`: Maximum number of iterations.
 
-Result: The set of accumulated labels of each node.
-
-```bash
-GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"start_label_attribute\":\"start_attr\",\"synchronous\":false,\"backwards\":false,\"maximum_supersteps\":500}" "$ENGINE_URL/v1/attributepropagation"
-```
+The result is the set of accumulated labels of each node.
 
 {{< comment >}} Work in progress
 #### Custom Python code
@@ -954,7 +1150,7 @@ Parameters:
   dict must represent the node ID. The value can be of any type.
 - `use_cugraph`: Use cugraph (or regular pandas/pyarrow).
 
-Result: Depends on the algorithm. If multiple values are returned for a single
+The result depends on the algorithm. If multiple values are returned for a single
 node, a JSON object with multiple keys is stored. <!-- TODO: verify -->
 
 ```bash
@@ -965,11 +1161,39 @@ curl -H "Authorization: bearer $ADB_TOKEN" -XPOST -d "{\"graph_id\":$GRAPH_ID,\"
 
 ### Store job results
 
-`POST <ENGINE_URL>/v1/storeresults`
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+POST https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/storeresults
+```
+
+**Example:**
+
+```bash
+JOB_ID="123"
+curl -H "Authorization: bearer $ADB_TOKEN" -X POST -d "{\"database\":\"_system\",\"target_collection\":\"coll\",\"job_ids\":[$JOB_ID],\"attribute_names\":[\"attr\"]}" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/storeresults"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+POST https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/storeresults
+```
+
+**Example:**
+
+```bash
+JOB_ID="123"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -X POST -d "{\"database\":\"_system\",\"target_collection\":\"coll\",\"job_ids\":[$JOB_ID],\"attribute_names\":[\"attr\"]}" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/storeresults"
+```
+
+{{< /tab >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/storeresults`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/storeresults`
+{{< /tabs >}}
 
 You need to specify to which ArangoDB `database` and `target_collection` to save
 the results to. They need to exist already.
@@ -992,95 +1216,226 @@ Parameters:
 - `parallelism`
 - `batch_size`
 
+### List all jobs
+
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
+
+```
+GET https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs
+```
+
+**Example:**
+
 ```bash
-JOB_ID="123"
-curl -H "Authorization: bearer $ADB_TOKEN" -X POST -d "{\"database\":\"_system\",\"target_collection\":\"coll\",\"job_ids\":[$JOB_ID],\"attribute_names\":[\"attr\"]}" "$ENGINE_URL/v1/storeresults"
+curl -H "Authorization: bearer $ADB_TOKEN" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/jobs"
 ```
 
-### List all jobs
+{{< /tab >}}
 
-`GET <ENGINE_URL>/v1/jobs`
+{{< tab "Arango Managed Platform (AMP)" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs`
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs
+```
 
-List all active and finished jobs.
+**Example:**
 
 ```bash
-curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/jobs"
 ```
 
+{{< /tab >}}
+
+{{< /tabs >}}
+
+List all active and finished jobs.
+
 ### Get a job
 
-`GET <ENGINE_URL>/v1/jobs/<JOB_ID>`
+{{< tabs "platforms" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs/<JOB_ID>`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs/<JOB_ID>`
+{{< tab "AI Data Platform" >}}
 
-Get detailed information about a specific job.
+```
+GET https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs/<JOB_ID>
+```
+
+**Example:**
 
 ```bash
 JOB_ID="123"
-curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/jobs/$JOB_ID"
+curl -H "Authorization: bearer $ADB_TOKEN" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/jobs/$JOB_ID"
 ```
 
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs/<JOB_ID>
+```
+
+**Example:**
+
+```bash
+JOB_ID="123"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/jobs/$JOB_ID"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
+
+Get detailed information about a specific job.
+
 ### Delete a job
 
-`DELETE <ENGINE_URL>/v1/jobs/<JOB_ID>`
+{{< tabs "platforms" >}}
+
+{{< tab "AI Data Platform" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs/<JOB_ID>`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs/<JOB_ID>`
+```
+DELETE https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/jobs/<JOB_ID>
+```
 
-Delete a specific job.
+**Example:**
 
 ```bash
 JOB_ID="123"
-curl -H "Authorization: bearer $ADB_TOKEN" -X DELETE "$ENGINE_URL/v1/jobs/$JOB_ID"
+curl -H "Authorization: bearer $ADB_TOKEN" -X DELETE "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/jobs/$JOB_ID"
 ```
 
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+DELETE https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/jobs/<JOB_ID>
+```
+
+**Example:**
+
+```bash
+JOB_ID="123"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -X DELETE "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/jobs/$JOB_ID"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
+
+Delete a specific job.
+
 ### List all graphs
 
-`GET <ENGINE_URL>/v1/graphs`
+{{< tabs "platforms" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs`
+{{< tab "AI Data Platform" >}}
 
-List all loaded sets of graph data that reside in the memory of the engine node.
+```
+GET https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs
+```
+
+**Example:**
+
+```bash
+curl -H "Authorization: bearer $ADB_TOKEN" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/graphs"
+```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs
+```
+
+**Example:**
 
 ```bash
-curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/graphs"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/graphs"
 ```
 
+{{< /tab >}}
+
+{{< /tabs >}}
+
+List all loaded sets of graph data that reside in the memory of the engine node.
+
 ### Get a graph
 
-`GET <ENGINE_URL>/v1/graphs/<GRAPH_ID>`
+{{< tabs "platforms" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs/<GRAPH_ID>`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs/<GRAPH_ID>`
+{{< tab "AI Data Platform" >}}
 
-Get detailed information about a specific set of graph data.
+```
+GET https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs/<GRAPH_ID>
+```
+
+**Example:**
 
 ```bash
 GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" "$ENGINE_URL/v1/graphs/$GRAPH_ID"
+curl -H "Authorization: bearer $ADB_TOKEN" "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/graphs/$GRAPH_ID"
 ```
 
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+GET https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs/<GRAPH_ID>
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/graphs/$GRAPH_ID"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
+
+Get detailed information about a specific set of graph data.
+
 ### Delete a graph
 
-`DELETE <ENGINE_URL>/v1/graphs/<GRAPH_ID>`
+{{< tabs "platforms" >}}
 
-**Examples:**
-- AI Data Platform: `https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs/<GRAPH_ID>`
-- AMP: `https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs/<GRAPH_ID>`
+{{< tab "AI Data Platform" >}}
 
-Delete a specific set of graph data, removing it from the memory of the engine node.
+```
+DELETE https://<EXTERNAL_ENDPOINT>:8529/gral/<SERVICE_ID>/v1/graphs/<GRAPH_ID>
+```
+
+**Example:**
 
 ```bash
 GRAPH_ID="234"
-curl -H "Authorization: bearer $ADB_TOKEN" -X DELETE "$ENGINE_URL/v1/graphs/$GRAPH_ID"
+curl -H "Authorization: bearer $ADB_TOKEN" -X DELETE "https://ai-data-platform.arango.com:8529/gral/tqcge/v1/graphs/$GRAPH_ID"
 ```
+
+{{< /tab >}}
+
+{{< tab "Arango Managed Platform (AMP)" >}}
+
+```
+DELETE https://<APPLICATION_ENDPOINT>:8829/graph-analytics/engines/<ENGINE_ID>/v1/graphs/<GRAPH_ID>
+```
+
+**Example:**
+
+```bash
+GRAPH_ID="234"
+curl -H "Authorization: bearer $ARANGO_GRAPH_TOKEN" -X DELETE "https://a1b2c3d4e5f6.arangodb.cloud:8829/graph-analytics/engines/zYxWvU9876/v1/graphs/$GRAPH_ID"
+```
+
+{{< /tab >}}
+
+{{< /tabs >}}
+
+Delete a specific set of graph data, removing it from the memory of the engine node.