Docs / Reference / read: why

read: why.

Any unit to the chain of reasons, from this unit back to its first cause

Figure 1POST /v1/read/whyspecified

The caller sends WhyInput to /v1/read/why. The platform returns a card whose body is WhyAnswer.

POST/v1/read/why

Why is this not ready; why is this not ready. The call needs the user rung under a token with the read grant, and it is served by the platform.

The route takes WhyInput and returns a card whose body is WhyAnswer.

Request body#

The request body is WhyInput.

field	type	required	note
`unit`	UnitRef	yes

Response#

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

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 user rung and a token with the read grant. The platform serves this route.

Example#

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

Example

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

import { client } from "@scale/sdk";
const answer = await client.read.why({
    "unit": {
      "id": "…",
      "kind": "…"
    }
  });
// answer.body is a WhyAnswer. answer.foot holds the basis, the scope and the time.

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

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

MCP tool#

The MCP tool si.read.why takes the same input and returns the same card. The tool only reads data. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/WhyAnswer. The tool’s page describes it.

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

{
  "unit": {
    "id": "…",
    "kind": "…"
  }
}

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

Claims#

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