work: lay strategy.

Lays one strategy on one twin, with the bounds of the run to The call returns the simulation whose interventions are the strategy's armed plays, then the frame

Request body#

The request body is LayStrategyInput.

Response#

The route returns a card whose body is MarketSimulation. Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true. This route runs as a long step and returns a task with status 202. POST /v1/work/status returns the task’s progress, and POST /v1/work/cancel stops the task.

Headers#

A caller needs the strategy rung and a token with the work grant. The platform serves this route.

Example#

The example sends the smallest body that LayStrategyInput allows. The build validates it against the schema of LayStrategyInput.

curl -X POST https://api.scaleintelligence.co/v1/work/lay_strategy \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "twin": "…", "strategy": "…" }'

import { client } from "@scale/sdk";
const answer = await client.work.lay_strategy({
    "twin": "…",
    "strategy": "…"
  });
// answer.body is a MarketSimulation. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/work/lay_strategy",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "twin": "…",
      "strategy": "…"
    }).json()

let answer: Card = client.post("https://api.scaleintelligence.co/v1/work/lay_strategy")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&LayStrategyInput { /* the fields of the page */ }).send().await?.json().await?;

MCP tool#

The MCP tool si.work.lay_strategy takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/MarketSimulation. The tool’s page describes it.

POST /v1/work/lay_strategy
Scale-Scope: …
Scale-As-True-On: …
Scale-As-Known-On: …
Scale-Key: …
content-type: application/json

{
  "twin": "…",
  "strategy": "…"
}