Scale Intelligence■ Docs
Docs / Reference / work: local procedure

work: local procedure.

A named procedure whose inputs are files in the workspace to a task run by the app with its steps in the app's own journal, resumable

Figure 1POST /v1/work/local_procedurespecified
CALLERyour app or an agentholds the keyAPI GATEWAY/v1/work/local_procedure4 headersCORE: WORKrung strategygrant workRECORDreads or writesTASK, 202body TaskThe input is LocalProcedureInput. Every response carries the contract's hash.flows forwardthe result
The caller sends LocalProcedureInput to /v1/work/local_procedure. The platform returns a card whose body is Task.
POST/v1/work/local_procedurea task, 202

From the local server’s own. The call needs the strategy rung under a token with the work grant, and it is served by the installed app.

The route takes LocalProcedureInput and returns a card whose body is Task.

Request body#

The request body is LocalProcedureInput.

fieldtyperequirednote
procedureNamedProcedureyes
inputsjsonno

Response#

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

headerrequiredmeaning
Scale-Scopeyesthe scope the call runs in: tenant/, then /brand/, then /strategy/
Scale-As-True-Onnothe date the facts must have been true on; defaults to now
Scale-As-Known-Onnothe date the facts must have been known on; defaults to now
Scale-Keynofor a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing

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

Example#

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

Example
curl -X POST https://api.scaleintelligence.co/v1/work/local_procedure \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "procedure": "…" }'
import { client } from "@scale/sdk";
const answer = await client.work.local_procedure({
    "procedure": "…"
  });
// answer.body is a Task. answer.foot holds the basis, the scope and the time.
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/work/local_procedure",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "procedure": "…"
    }).json()
let answer: Card = client.post("https://api.scaleintelligence.co/v1/work/local_procedure")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&LocalProcedureInput { /* the fields of the page */ }).send().await?.json().await?;

MCP tool#

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

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

{
  "procedure": "…"
}
Without a key, this page shows the request only. The request body is LocalProcedureInput, and the route returns a card whose body is Task.

Claims#

claimstateroute or tool
The platform serves the route /v1/work/local_procedure at contract 0476e35e6e275db5.target/v1/work/local_procedure