node-red-contrib-vectorprime 0.1.6 → 0.1.7

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "node-red-contrib-vectorprime",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "VectorPrime Decision Kernel node for Node-RED",
   "main": "vectorprime.js",
   "license": "MIT",

package/vectorprime.html

@@ -27,24 +27,25 @@
   </div>
 </script>
 
-<!-- ✅ HELP TEXT (this fixes "no information available" for config node) -->
+<!-- ✅ Help text for the config node -->
 <script type="text/html" data-help-name="vectorprime-config">
   <p><b>VectorPrime Config</b></p>
 
   <p>
-    Stores the VectorPrime backend URL and your API key securely using Node-RED credentials.
-    This is shared across VectorPrime nodes so you only configure it once.
+    Stores your VectorPrime API connection details securely using Node-RED credentials.
+    This keeps your API key <b>out of flow exports</b>.
   </p>
 
-  <p><b>Quick Start</b></p>
+  <h3>Quick setup</h3>
   <ol>
-    <li>Leave <b>Base URL</b> as default unless you self-host VectorPrime.</li>
-    <li>Click <b>Get Free Key</b> to generate a key instantly.</li>
-    <li>Hit <b>Done</b> to save.</li>
+    <li>Leave Base URL as default (or set your own hosted backend).</li>
+    <li>Click <b>Get Free Key</b> to generate a starter key instantly.</li>
+    <li>Use this config in one or more VectorPrime nodes.</li>
   </ol>
 
-  <p style="margin-top:8px; font-size:12px; color:#666;">
-    Tip: Your API key is not exported in flow JSON and stays encrypted inside Node-RED credentials.
+  <p>
+    <b>Default Base URL:</b><br/>
+    <code>https://vectorprime-kernel-backend.onrender.com</code>
   </p>
 </script>
 
@@ -89,6 +90,7 @@
               return;
             }
 
+            // Call backend directly from the editor
             const resp = await fetch(`${baseUrl}/v1/keys/free`, {
               method: "POST",
               headers: { "Content-Type": "application/json" },
@@ -124,10 +126,6 @@
   })();
 </script>
 
-<!-- ========================= -->
-<!-- ✅ VectorPrime Rank Node   -->
-<!-- ========================= -->
-
 <script type="text/html" data-template-name="vectorprime-rank">
   <div class="form-row">
     <label for="node-input-name"><i class="fa fa-tag"></i> Name</label>
@@ -146,54 +144,48 @@
 
   <div class="form-row">
     <div style="font-size:12px; color:#666;">
-      ✅ Sends <code>msg.payload</code> to VectorPrime and returns results in <code>msg.payload</code>.
+      ✅ Sends <code>msg.payload</code> to VectorPrime and returns ranked results in <code>msg.payload</code>.
     </div>
   </div>
 </script>
 
-<!-- ✅ HELP TEXT (this fixes your tooltip + makes it MARKETABLE) -->
+<!-- ✅ Help text for the rank node (THIS controls the palette hover tooltip content) -->
 <script type="text/html" data-help-name="vectorprime-rank">
   <p><b>Rank Decision (VectorPrime)</b></p>
 
   <p>
-    Instantly ranks options by <b>best next action</b> using the VectorPrime Decision Kernel.
-    Use this when your flow needs to choose the best outcome from multiple choices — fast and deterministically.
+    Instantly rank tasks, events, or choices by <b>priority + urgency</b> using the VectorPrime Decision Kernel.
+    Perfect for building flows that automatically pick the <b>best next action</b>.
   </p>
 
-  <p><b>Most valuable use-cases (why developers install this)</b></p>
+  <h3>Best use cases</h3>
   <ul>
-    <li><b>Automation routing:</b> pick which workflow runs next based on priority + risk</li>
-    <li><b>Incident response:</b> rank mitigation steps during outages (fastest safe fix)</li>
-    <li><b>Agent coordination:</b> choose the best tool/action from multiple agent outputs</li>
-    <li><b>Ops decisioning:</b> prioritize tickets/tasks using a deterministic decision score</li>
+    <li><b>Incident response:</b> Rank alerts and decide what to fix first</li>
+    <li><b>Ops & automation:</b> Choose the next job to run when resources are limited</li>
+    <li><b>AI agents:</b> Pick the best tool/action based on outcome + risk</li>
+    <li><b>Queues & tickets:</b> Prioritize support tickets, backlog items, escalations</li>
+    <li><b>Workflow routing:</b> Route messages/events to the right handler by importance</li>
   </ul>
 
-  <p><b>Input</b></p>
-  <pre>{
-  "decision_id": "any-string",
-  "prompt": "What should we do next?",
-  "options": [
-    {"id":"a","label":"Option A"},
-    {"id":"b","label":"Option B"}
-  ],
-  "engine": "classical",
-  "seed": 123
-}</pre>
-
-  <p><b>Output</b></p>
+  <h3>Input</h3>
+  <p>
+    Expects <code>msg.payload</code> to be your decision set / tasks object (JSON).
+  </p>
+
+  <h3>Output</h3>
   <p>
-    Returns the ranking result in <code>msg.payload</code> (ordered options + scores/probabilities depending on engine).
+    Returns the VectorPrime response in <code>msg.payload</code>, including ranked results.
   </p>
 
-  <p style="margin-top:8px; font-size:12px; color:#666;">
-    Tip: If the free tier limit is reached, the response includes an upgrade URL so flows can upgrade cleanly.
+  <h3>Tip</h3>
+  <p>
+    If you hit a free-tier limit, the response may include an upgrade URL so your flow can continue.
   </p>
 </script>
 
 <script type="text/javascript">
   RED.nodes.registerType("vectorprime-rank", {
-    category: "network",
-    paletteLabel: "Rank Decision (VectorPrime)",
+    category: "network",                 // ✅ moved to Network
     color: "#2563EB",
     defaults: {
       name: { value: "" },
@@ -203,6 +195,10 @@
     inputs: 1,
     outputs: 1,
     icon: "font-awesome/fa-bolt",
+
+    // ✅ This makes the palette show a human label instantly
+    paletteLabel: "Rank Decision (VectorPrime)",
+
     label: function () {
       return this.name || "Rank Decision (VectorPrime)";
     }