@mindstudio-ai/agent 0.1.98 → 0.1.100

package/llms.txt

@@ -19,7 +19,7 @@ For specific use cases:
 - **Pre-built agents**: Call `listAgents()` to see what's available → `runAgent({ appId })` to execute one. **Important:** Not all agents are configured for API use. Do not try to run an agent just because it appears in the list — only run agents the user specifically asks you to run.
 - **Model selection**: Call `listModelsSummary()` or `listModelsSummaryByType("llm_chat")` to browse models, then pass the model ID as `modelOverride.model` to actions like `generateText`. Use the summary endpoints (not `listModels`) to keep token usage low.
 - **Cost estimation**: AI-powered actions (text generation, image generation, video, audio, etc.) cost money. Call `estimateStepCost(stepType, stepInput)` before running these and confirm with the user before proceeding — unless they've explicitly given permission to go ahead. Non-AI actions (data lookups, OAuth connectors, etc.) are generally free.
-- **Task agents**: For multi-step tasks that need autonomous tool use (research, content creation, data enrichment), use `runTask()`. Provide a prompt, input, tools, a structured output example, and a tool-use model id. The platform runs a tool-use loop — calling the model, executing tools, feeding results back — until structured output is produced. Tools are SDK action names and/or your own app methods, written as `{ appMethod: "saveVendor", description: "when to use it" }`. App methods run as the user who invoked the method that started the task, with their roles, so the agent can read and write app state on their behalf. Example: `runTask({ prompt: "Research this restaurant and save it", input: { name: "Tartine" }, tools: ["searchGoogle", "fetchUrl", { appMethod: "saveRestaurant", description: "Persist the researched restaurant." }], structuredOutputExample: '{"name":"...","url":"..."}', model: yourModelId })`. Pass a current tool-use model id (call `listModels` or ask). Don't hardcode one.
+- **Task agents**: For multi-step tasks that need autonomous tool use (research, content creation, data enrichment), use `runTask()`. Provide a prompt, input, tools, an output contract, and a tool-use model id. The SDK runs a tool-use loop — calling the model, executing tools, feeding results back — until structured output is produced. Tools are SDK action names and/or your own app methods, written as `{ appMethod: "saveVendor", description: "when to use it" }`. App methods run as the user who invoked the method that started the task, with their roles, so the agent can read and write app state on their behalf. Prefer `outputSchema` for the output contract: plain JSON Schema (`type`/`properties`/`required`/`enum`/`items`; nullable via type arrays like `["string","null"]` — no `oneOf`/`$ref`/`nullable`). Output is validated every turn with automatic repair, `result.output` is fully typed from the schema (no generic argument, no `parsedSuccessfully` check), and the call throws `MindStudioError` code `task_output_schema_mismatch` if the agent cannot produce conforming output. Example: `runTask({ prompt: "Research this restaurant and save it", input: { name: "Tartine" }, tools: ["searchGoogle", "fetchUrl", { appMethod: "saveRestaurant", description: "Persist the researched restaurant." }], outputSchema: { type: "object", properties: { name: { type: "string" }, url: { type: ["string", "null"] } }, required: ["name"] }, model: yourModelId })`. The legacy `structuredOutputExample` option (an example object the model imitates) still works but is unvalidated — check `result.parsedSuccessfully` before using its output. Pass a current tool-use model id (call `listModels` or ask). Don't hardcode one.
 
 ## Install
 
@@ -179,7 +179,7 @@ result.content;              // step-specific output field
 result.$appId;               // string — app ID for this execution
 result.$threadId;            // string — thread ID for this execution
 result.$rateLimitRemaining;  // number | undefined — API calls remaining in rate limit window
-result.$billingCost;         // number | undefined — cost in credits for this call
+result.$billingCost;         // number | undefined — cost in nanodollars (1e-9 USD; divide by 1e9 for dollars, e.g. 40000000 = $0.04)
 result.$billingEvents;       // object[] | undefined — itemized billing events
 ```
 
@@ -239,8 +239,8 @@ result.results;          // BatchStepResult[] — same order as input
 result.results[0].stepType;  // string
 result.results[0].output;    // object | undefined (step output on success)
 result.results[0].error;     // string | undefined (error message on failure)
-result.results[0].billingCost; // number | undefined (cost on success)
-result.totalBillingCost;  // number | undefined
+result.results[0].billingCost; // number | undefined (cost in nanodollars on success)
+result.totalBillingCost;  // number | undefined — nanodollars (divide by 1e9 for USD)
 result.appId;            // string
 result.threadId;         // string
 ```
@@ -1769,9 +1769,9 @@ Output:
   estimates?: {
     eventType: string;       // Billing event type
     label: string;           // Human-readable cost label
-    unitPrice: number;       // Price per unit in billing units
+    unitPrice: number;       // Price per unit in nanodollars (1e-9 USD)
     unitType: string;        // What constitutes a unit (e.g. "token", "request")
-    estimatedCost?: number;  // Estimated total cost, or null if not estimable
+    estimatedCost?: number;  // Estimated total cost in nanodollars, or null if not estimable
     quantity: number;        // Number of billable units
   }[]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/agent",
-  "version": "0.1.98",
+  "version": "0.1.100",
   "description": "TypeScript SDK for MindStudio direct step execution",
   "type": "module",
   "main": "./dist/index.js",