unitysvc-data 0.2.3__tar.gz → 0.2.5__tar.gz

{unitysvc_data-0.2.3/src/unitysvc_data.egg-info → unitysvc_data-0.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: unitysvc-data
-Version: 0.2.3
+Version: 0.2.5
 Summary: Standard examples and presets for UnitySVC data packages
 Author-email: Bo Peng <bo.peng@unitysvc.com>
 Maintainer-email: Bo Peng <bo.peng@unitysvc.com>

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "unitysvc-data"
-version = "0.2.3"
+version = "0.2.5"
 description = "Standard examples and presets for UnitySVC data packages"
 readme = "README.md"
 authors = [{ name = "Bo Peng", email = "bo.peng@unitysvc.com" }]

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/_manifest.json

@@ -22,6 +22,9 @@
     "llm_code_example_chat_dashscope_javascript": "llm_code_example_chat_dashscope_javascript_v1",
     "llm_code_example_chat_dashscope_requests": "llm_code_example_chat_dashscope_requests_v1",
     "llm_code_example_chat_dashscope_shell": "llm_code_example_chat_dashscope_shell_v1",
+    "llm_code_example_chat_dashscope_text_javascript": "llm_code_example_chat_dashscope_text_javascript_v1",
+    "llm_code_example_chat_dashscope_text_requests": "llm_code_example_chat_dashscope_text_requests_v1",
+    "llm_code_example_chat_dashscope_text_shell": "llm_code_example_chat_dashscope_text_shell_v1",
     "llm_code_example_cohere": "llm_code_example_cohere_v1",
     "llm_code_example_embed_dashscope_javascript": "llm_code_example_embed_dashscope_javascript_v1",
     "llm_code_example_embed_dashscope_requests": "llm_code_example_embed_dashscope_requests_v1",
@@ -80,6 +83,7 @@
     "llm_connectivity_anthropic": "llm_connectivity_anthropic_v1",
     "llm_connectivity_asr_dashscope": "llm_connectivity_asr_dashscope_v1",
     "llm_connectivity_chat_dashscope": "llm_connectivity_chat_dashscope_v1",
+    "llm_connectivity_chat_dashscope_text": "llm_connectivity_chat_dashscope_text_v1",
     "llm_connectivity_embed": "llm_connectivity_embed_v1",
     "llm_connectivity_embed_dashscope": "llm_connectivity_embed_dashscope_v1",
     "llm_connectivity_embed_image": "llm_connectivity_embed_image_v1",
@@ -1158,7 +1162,7 @@
     "llm_code_example_asr_dashscope_javascript_v1": {
       "applies_to": {
         "capability": "speech-to-text",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -1182,7 +1186,7 @@
     "llm_code_example_asr_dashscope_requests_v1": {
       "applies_to": {
         "capability": "speech-to-text",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -1209,7 +1213,7 @@
     "llm_code_example_asr_dashscope_shell_v1": {
       "applies_to": {
         "capability": "speech-to-text",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -1317,7 +1321,7 @@
     "llm_code_example_chat_dashscope_javascript_v1": {
       "applies_to": {
         "capability": "chat",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -1341,7 +1345,7 @@
     "llm_code_example_chat_dashscope_requests_v1": {
       "applies_to": {
         "capability": "chat",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -1368,7 +1372,7 @@
     "llm_code_example_chat_dashscope_shell_v1": {
       "applies_to": {
         "capability": "chat",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -1389,6 +1393,81 @@
       "source_readme": "llm/dashscope-chat-shell/README.md",
       "version": 1
     },
+    "llm_code_example_chat_dashscope_text_javascript_v1": {
+      "applies_to": {
+        "capability": "chat",
+        "dialect": "dashscope_text",
+        "upstream": "dashscope"
+      },
+      "category": "code_example",
+      "description": "JavaScript example: send a chat completion to a DashScope text-generation endpoint with fetch",
+      "example_file": "llm/dashscope-text-chat-javascript/code-example-v1.js.j2",
+      "is_active": true,
+      "is_public": true,
+      "meta": {
+        "min_expected_metrics": {
+          "input_tokens": 1,
+          "output_tokens": 1
+        },
+        "variant": "Chat (DashScope text)"
+      },
+      "mime_type": "javascript",
+      "parameters": {},
+      "preset_name": "llm_code_example_chat_dashscope_text_javascript",
+      "source_readme": "llm/dashscope-text-chat-javascript/README.md",
+      "version": 1
+    },
+    "llm_code_example_chat_dashscope_text_requests_v1": {
+      "applies_to": {
+        "capability": "chat",
+        "dialect": "dashscope_text",
+        "upstream": "dashscope"
+      },
+      "category": "code_example",
+      "description": "Python example: send a chat completion to a DashScope text-generation endpoint using the requests library",
+      "example_file": "llm/dashscope-text-chat-requests/code-example-v1.py.j2",
+      "is_active": true,
+      "is_public": true,
+      "meta": {
+        "min_expected_metrics": {
+          "input_tokens": 1,
+          "output_tokens": 1
+        },
+        "requirements": [
+          "requests"
+        ],
+        "variant": "Chat (DashScope text)"
+      },
+      "mime_type": "python",
+      "parameters": {},
+      "preset_name": "llm_code_example_chat_dashscope_text_requests",
+      "source_readme": "llm/dashscope-text-chat-requests/README.md",
+      "version": 1
+    },
+    "llm_code_example_chat_dashscope_text_shell_v1": {
+      "applies_to": {
+        "capability": "chat",
+        "dialect": "dashscope_text",
+        "upstream": "dashscope"
+      },
+      "category": "code_example",
+      "description": "Shell example: send a chat completion to a DashScope text-generation endpoint via curl",
+      "example_file": "llm/dashscope-text-chat-shell/code-example-v1.sh.j2",
+      "is_active": true,
+      "is_public": true,
+      "meta": {
+        "min_expected_metrics": {
+          "input_tokens": 1,
+          "output_tokens": 1
+        },
+        "variant": "Chat (DashScope text)"
+      },
+      "mime_type": "bash",
+      "parameters": {},
+      "preset_name": "llm_code_example_chat_dashscope_text_shell",
+      "source_readme": "llm/dashscope-text-chat-shell/README.md",
+      "version": 1
+    },
     "llm_code_example_cohere_v1": {
       "applies_to": {
         "capability": "chat",
@@ -2786,7 +2865,7 @@
     "llm_code_example_tts_dashscope_javascript_v1": {
       "applies_to": {
         "capability": "text-to-speech",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -2809,7 +2888,7 @@
     "llm_code_example_tts_dashscope_requests_v1": {
       "applies_to": {
         "capability": "text-to-speech",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -2835,7 +2914,7 @@
     "llm_code_example_tts_dashscope_shell_v1": {
       "applies_to": {
         "capability": "text-to-speech",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "code_example",
@@ -3228,7 +3307,7 @@
     "llm_connectivity_asr_dashscope_v1": {
       "applies_to": {
         "capability": "speech-to-text",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "connectivity_test",
@@ -3248,10 +3327,33 @@
       "source_readme": "llm/dashscope-asr-connectivity/README.md",
       "version": 1
     },
+    "llm_connectivity_chat_dashscope_text_v1": {
+      "applies_to": {
+        "capability": "chat",
+        "dialect": "dashscope_text",
+        "upstream": "dashscope"
+      },
+      "category": "connectivity_test",
+      "description": "Verify a DashScope text-generation endpoint by issuing a tiny request (chat)",
+      "example_file": "llm/dashscope-text-chat-connectivity/connectivity-v1.sh.j2",
+      "is_active": true,
+      "is_public": false,
+      "meta": {
+        "min_expected_metrics": {
+          "input_tokens": 1,
+          "output_tokens": 1
+        }
+      },
+      "mime_type": "bash",
+      "parameters": {},
+      "preset_name": "llm_connectivity_chat_dashscope_text",
+      "source_readme": "llm/dashscope-text-chat-connectivity/README.md",
+      "version": 1
+    },
     "llm_connectivity_chat_dashscope_v1": {
       "applies_to": {
         "capability": "chat",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "connectivity_test",
@@ -3366,7 +3468,7 @@
     "llm_connectivity_tts_dashscope_v1": {
       "applies_to": {
         "capability": "text-to-speech",
-        "dialect": "dashscope",
+        "dialect": "dashscope_multimodal",
         "upstream": "dashscope"
       },
       "category": "connectivity_test",

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-asr-connectivity/README.md

@@ -7,7 +7,7 @@ description = "Verify a DashScope-native endpoint by issuing a tiny request (spe
 is_active = true
 is_public = false
 meta = { min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "speech-to-text", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "speech-to-text", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-asr-connectivity
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-asr-javascript/README.md

@@ -7,7 +7,7 @@ description = "JavaScript example: transcribe audio on a DashScope-native endpoi
 is_active = true
 is_public = true
 meta = { variant = "Speech to text (DashScope)", min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "speech-to-text", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "speech-to-text", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-asr-javascript
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-asr-requests/README.md

@@ -7,7 +7,7 @@ description = "Python example: transcribe audio on a DashScope-native endpoint u
 is_active = true
 is_public = true
 meta = { variant = "Speech to text (DashScope)", requirements = ["requests"], min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "speech-to-text", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "speech-to-text", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-asr-requests
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-asr-shell/README.md

@@ -7,7 +7,7 @@ description = "Shell example: transcribe audio on a DashScope-native endpoint vi
 is_active = true
 is_public = true
 meta = { variant = "Speech to text (DashScope)", min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "speech-to-text", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "speech-to-text", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-asr-shell
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-chat-connectivity/README.md

@@ -7,7 +7,7 @@ description = "Verify a DashScope-native endpoint by issuing a tiny request (cha
 is_active = true
 is_public = false
 meta = { min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "chat", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "chat", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-chat-connectivity
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-chat-javascript/README.md

@@ -7,7 +7,7 @@ description = "JavaScript example: send a chat completion to a DashScope-native
 is_active = true
 is_public = true
 meta = { variant = "Chat (DashScope)", min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "chat", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "chat", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-chat-javascript
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-chat-requests/README.md

@@ -7,7 +7,7 @@ description = "Python example: send a chat completion to a DashScope-native endp
 is_active = true
 is_public = true
 meta = { variant = "Chat (DashScope)", requirements = ["requests"], min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "chat", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "chat", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-chat-requests
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

{unitysvc_data-0.2.3 → unitysvc_data-0.2.5}/src/unitysvc_data/examples/llm/dashscope-chat-shell/README.md

@@ -7,7 +7,7 @@ description = "Shell example: send a chat completion to a DashScope-native endpo
 is_active = true
 is_public = true
 meta = { variant = "Chat (DashScope)", min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
-applies_to = { capability = "chat", dialect = "dashscope", upstream = "dashscope" }
+applies_to = { capability = "chat", dialect = "dashscope_multimodal", upstream = "dashscope" }
 +++
 
 # llm / dashscope-chat-shell
@@ -35,4 +35,11 @@ the full native path, so the example posts to the service URL with no suffix.
 ## Versions
 
 ### v1 — initial release
-
+- **Amended in 0.2.4**: the dialect token is now `dashscope_multimodal`, not
+  `dashscope`. These examples send and read the multimodal shape — `content` as an
+  **array of parts** — which `aigc/multimodal-generation/generation` serves and
+  `aigc/text-generation/generation` rejects with `HTTP 400 InvalidParameter: url
+  error`. Naming the token after the shape is what lets a text-only model select
+  `dashscope_text` instead; a bare `dashscope` now selects neither, so a service
+  has to say which it speaks. Selection metadata only — nothing these examples do
+  has changed.

unitysvc_data-0.2.5/src/unitysvc_data/examples/llm/dashscope-text-chat-connectivity/README.md

@@ -0,0 +1,51 @@
++++
+preset_name = "llm_connectivity_chat_dashscope_text"
+category = "connectivity_test"
+mime_type = "bash"
+file = "connectivity.sh.j2"
+description = "Verify a DashScope text-generation endpoint by issuing a tiny request (chat)"
+is_active = true
+is_public = false
+meta = { min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
+applies_to = { capability = "chat", dialect = "dashscope_text", upstream = "dashscope" }
++++
+
+# llm / dashscope-text-chat-connectivity
+
+DashScope serves a TEXT-ONLY model at `aigc/text-generation/generation`,
+where `input.messages[].content` is a **string** and the reply carries
+`output.choices[].message.content` as a **string**. Its multimodal sibling
+(`aigc/multimodal-generation/generation`) takes and returns an **array of
+parts**, and the two are not interchangeable: posting either shape to the other
+path answers `HTTP 400 InvalidParameter: url error, please check url`. Verified
+in both directions against the live API.
+
+That is why the dialect token is `dashscope_text` rather than plain `dashscope` —
+the endpoint, the request shape and the response shape all move together, so they
+are one wire dialect, and a service must say which of the two it speaks. Neither
+is the default; a group naming a bare `dashscope` selects neither, which fails
+where it can be seen rather than sending the wrong shape.
+
+The request pins `parameters.result_format` to `"message"`. Text-generation
+returns whichever shape the MODEL defaults to otherwise — `output.text` for some,
+`output.choices[].message` for others — and a reader cannot be written against
+both. Pinning it makes the response shape a property of the request.
+
+Assertions check the payload rather than the status, because DashScope answers
+**200 with an error envelope**. They sit behind `{%- if not customer_display %}`
+so the published example stays clean.
+
+## Versions
+
+### v1 — initial release
+
+- The smallest useful request the text-generation endpoint takes.
+- Asserts the reply carries `"choices"`; a 2xx alone is not enough.
+- **Amended in 0.2.5**: `parameters.result_format` is now pinned to `"message"`.
+  Without it DashScope's text-generation returns whichever shape the MODEL
+  defaults to — `output.text` for some, `output.choices[].message` for others —
+  so an example that reads `choices` failed on half the catalog with
+  `Cannot read properties of undefined`. Probed both ways on `qwen-flash`:
+  absent gives `{"output":{"text":…}}`, `"message"` gives
+  `{"output":{"choices":[…]}}`. The reader is unchanged; the request now asks for
+  the shape it reads.

unitysvc_data-0.2.5/src/unitysvc_data/examples/llm/dashscope-text-chat-connectivity/connectivity-v1.sh.j2

@@ -0,0 +1,20 @@
+#!/bin/bash
+# DashScope connectivity probe (chat, text-generation): POST the smallest useful
+# request the endpoint takes and assert the reply really carries "choices".
+# A 2xx alone is not enough -- DashScope answers 200 with an error envelope.
+set -e -o pipefail
+
+: "${UNITYSVC_API_KEY:?UNITYSVC_API_KEY is not set}"
+
+response=$(curl --fail-with-body -sS "{{ service_base_url }}" \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer ${UNITYSVC_API_KEY}" \
+  -d '{"model": "{{ routing_key.model }}", "input": {"messages": [{"role": "user", "content": "Say this is a test"}]}, "parameters": {"max_tokens": 64, "result_format": "message"}}')
+
+echo "$response"
+{%- if not customer_display %}
+if ! printf '%s' "$response" | grep -q '"choices"'; then
+  echo 'unexpected response: no "choices" in the reply' >&2
+  exit 1
+fi
+{%- endif %}

unitysvc_data-0.2.5/src/unitysvc_data/examples/llm/dashscope-text-chat-javascript/README.md

@@ -0,0 +1,50 @@
++++
+preset_name = "llm_code_example_chat_dashscope_text_javascript"
+category = "code_example"
+mime_type = "javascript"
+file = "code-example.js.j2"
+description = "JavaScript example: send a chat completion to a DashScope text-generation endpoint with fetch"
+is_active = true
+is_public = true
+meta = { variant = "Chat (DashScope text)", min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
+applies_to = { capability = "chat", dialect = "dashscope_text", upstream = "dashscope" }
++++
+
+# llm / dashscope-text-chat-javascript
+
+DashScope serves a TEXT-ONLY model at `aigc/text-generation/generation`,
+where `input.messages[].content` is a **string** and the reply carries
+`output.choices[].message.content` as a **string**. Its multimodal sibling
+(`aigc/multimodal-generation/generation`) takes and returns an **array of
+parts**, and the two are not interchangeable: posting either shape to the other
+path answers `HTTP 400 InvalidParameter: url error, please check url`. Verified
+in both directions against the live API.
+
+That is why the dialect token is `dashscope_text` rather than plain `dashscope` —
+the endpoint, the request shape and the response shape all move together, so they
+are one wire dialect, and a service must say which of the two it speaks. Neither
+is the default; a group naming a bare `dashscope` selects neither, which fails
+where it can be seen rather than sending the wrong shape.
+
+The request pins `parameters.result_format` to `"message"`. Text-generation
+returns whichever shape the MODEL defaults to otherwise — `output.text` for some,
+`output.choices[].message` for others — and a reader cannot be written against
+both. Pinning it makes the response shape a property of the request.
+
+Assertions check the payload rather than the status, because DashScope answers
+**200 with an error envelope**. They sit behind `{%- if not customer_display %}`
+so the published example stays clean.
+
+## Versions
+
+### v1 — initial release
+
+- `fetch`, no SDK; throws with the response body on a non-2xx.
+- **Amended in 0.2.5**: `parameters.result_format` is now pinned to `"message"`.
+  Without it DashScope's text-generation returns whichever shape the MODEL
+  defaults to — `output.text` for some, `output.choices[].message` for others —
+  so an example that reads `choices` failed on half the catalog with
+  `Cannot read properties of undefined`. Probed both ways on `qwen-flash`:
+  absent gives `{"output":{"text":…}}`, `"message"` gives
+  `{"output":{"choices":[…]}}`. The reader is unchanged; the request now asks for
+  the shape it reads.

unitysvc_data-0.2.5/src/unitysvc_data/examples/llm/dashscope-text-chat-javascript/code-example-v1.js.j2

@@ -0,0 +1,25 @@
+async function main() {
+  const response = await fetch("{{ service_base_url }}", {
+    method: "POST",
+    headers: {
+      "Content-Type": "application/json",
+      Authorization: `Bearer ${process.env.UNITYSVC_API_KEY}`,
+    },
+    body: JSON.stringify({"model": "{{ routing_key.model }}", "input": {"messages": [{"role": "user", "content": "Say this is a test"}]}, "parameters": {"max_tokens": 64, "result_format": "message"}}),
+  });
+  if (!response.ok) {
+    throw new Error(`HTTP ${response.status}: ${await response.text()}`);
+  }
+  const data = await response.json();
+  console.log(data.output.choices[0].message.content);
+{%- if not customer_display %}
+  if (!data.output?.choices?.length) {
+      throw new Error("no choices in the reply");
+    }
+{%- endif %}
+}
+
+main().catch((err) => {
+  console.error(err.message);
+  process.exit(1);
+});

unitysvc_data-0.2.5/src/unitysvc_data/examples/llm/dashscope-text-chat-requests/README.md

@@ -0,0 +1,53 @@
++++
+preset_name = "llm_code_example_chat_dashscope_text_requests"
+category = "code_example"
+mime_type = "python"
+file = "code-example.py.j2"
+description = "Python example: send a chat completion to a DashScope text-generation endpoint using the requests library"
+is_active = true
+is_public = true
+meta = { variant = "Chat (DashScope text)", requirements = ["requests"], min_expected_metrics = { input_tokens = 1, output_tokens = 1 } }
+applies_to = { capability = "chat", dialect = "dashscope_text", upstream = "dashscope" }
++++
+
+# llm / dashscope-text-chat-requests
+
+DashScope serves a TEXT-ONLY model at `aigc/text-generation/generation`,
+where `input.messages[].content` is a **string** and the reply carries
+`output.choices[].message.content` as a **string**. Its multimodal sibling
+(`aigc/multimodal-generation/generation`) takes and returns an **array of
+parts**, and the two are not interchangeable: posting either shape to the other
+path answers `HTTP 400 InvalidParameter: url error, please check url`. Verified
+in both directions against the live API.
+
+That is why the dialect token is `dashscope_text` rather than plain `dashscope` —
+the endpoint, the request shape and the response shape all move together, so they
+are one wire dialect, and a service must say which of the two it speaks. Neither
+is the default; a group naming a bare `dashscope` selects neither, which fails
+where it can be seen rather than sending the wrong shape.
+
+The request pins `parameters.result_format` to `"message"`. Text-generation
+returns whichever shape the MODEL defaults to otherwise — `output.text` for some,
+`output.choices[].message` for others — and a reader cannot be written against
+both. Pinning it makes the response shape a property of the request.
+
+Assertions check the payload rather than the status, because DashScope answers
+**200 with an error envelope**. They sit behind `{%- if not customer_display %}`
+so the published example stays clean.
+
+## Versions
+
+### v1 — initial release
+
+- POST `model` + `input.messages` with `content` as a string.
+- No vendor SDK; `requests` only.
+- Raises with the response body on a non-2xx, rather than `raise_for_status`,
+  which discards it.
+- **Amended in 0.2.5**: `parameters.result_format` is now pinned to `"message"`.
+  Without it DashScope's text-generation returns whichever shape the MODEL
+  defaults to — `output.text` for some, `output.choices[].message` for others —
+  so an example that reads `choices` failed on half the catalog with
+  `Cannot read properties of undefined`. Probed both ways on `qwen-flash`:
+  absent gives `{"output":{"text":…}}`, `"message"` gives
+  `{"output":{"choices":[…]}}`. The reader is unchanged; the request now asks for
+  the shape it reads.

unitysvc_data-0.2.5/src/unitysvc_data/examples/llm/dashscope-text-chat-requests/code-example-v1.py.j2

@@ -0,0 +1,20 @@
+import os
+
+import requests
+
+response = requests.post(
+    "{{ service_base_url }}",
+    headers={
+        "Authorization": f"Bearer {os.environ['UNITYSVC_API_KEY']}",
+        "Content-Type": "application/json",
+    },
+    json={"model": "{{ routing_key.model }}", "input": {"messages": [{"role": "user", "content": "Say this is a test"}]}, "parameters": {"max_tokens": 64, "result_format": "message"}},
+)
+if response.status_code >= 400:
+    raise RuntimeError(f"HTTP {response.status_code} from {response.url}: {response.text}")
+data = response.json()
+print(data["output"]["choices"][0]["message"]["content"])
+{%- if not customer_display %}
+if not data.get("output", {}).get("choices"):
+    raise SystemExit("no choices in the reply")
+{%- endif %}