Docs / Reference / act: deepen

act: deepen.

An observation, and the depth: fetched in full, or given meaning to a deepening

Figure 1POST /v1/act/deepenspecified

The caller sends DeepenInput to /v1/act/deepen. The platform returns a card whose body is Deepening.

POST/v1/act/deepena task, 202

Ask for depth. The call needs the strategy rung under a token with the act grant, and it is served by the platform.

The route takes DeepenInput and returns a card whose body is Deepening.

Request body#

The request body is DeepenInput.

field	type	required
`observation`	`id`	yes
`depth`	`one of fetch \| embed \| both`	yes
`asked_by`	UnitRef	yes

Response#

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

header	required	meaning
`Scale-Scope`	yes	the scope the call runs in: tenant/, then /brand/, then /strategy/
`Scale-As-True-On`	no	the date the facts must have been true on; defaults to now
`Scale-As-Known-On`	no	the date the facts must have been known on; defaults to now
`Scale-Key`	no	for 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 act grant. The platform serves this route.

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/act/deepen \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "observation": "…", "depth": "fetch", "asked_by": { "id": "…", "kind": "…" } }'

import { client } from "@scale/sdk";
const answer = await client.act.deepen({
    "observation": "…",
    "depth": "fetch",
    "asked_by": {
      "id": "…",
      "kind": "…"
    }
  });
// answer.body is a Deepening. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/deepen",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "observation": "…",
      "depth": "fetch",
      "asked_by": {
        "id": "…",
        "kind": "…"
      }
    }).json()

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

MCP tool#

The MCP tool si.act.deepen 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/Deepening. The tool’s page describes it.

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

{
  "observation": "…",
  "depth": "fetch",
  "asked_by": {
    "id": "…",
    "kind": "…"
  }
}

Without a key, this page shows the request only. The request body is DeepenInput, and the route returns a card whose body is Deepening.

Claims#

claim	state	route or tool
The platform serves the route /v1/act/deepen at contract 0476e35e6e275db5.	target	`/v1/act/deepen`