work: mine.

The caller to every run the caller started that is still running, each with what it has done, whether it may be stopped, and the tool that stops it

Request body#

The request body is empty.

Response#

The route returns a card whose body is MyWork. 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.

Headers#

A caller needs the user rung and a token with the work grant. The platform or the desktop app serves this route.

Example#

The example sends an empty body.

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

import { client } from "@scale/sdk";
const answer = await client.work.mine({});
// answer.body is a MyWork. answer.foot holds the basis, the scope and the time.

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

let answer: Card = client.post("https://api.scaleintelligence.co/v1/work/mine")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&()).send().await?.json().await?;

MCP tool#

The MCP tool si.work.mine 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/MyWork. The tool’s page describes it.

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

{}