Scale Intelligence■ Docs
Docs / Reference / read: board

read: board.

The board and a period to the board with every tile's numbers, each with its basis and its population

Figure 1POST /v1/read/boardspecified
CALLERyour app or an agentholds the keyAPI GATEWAY/v1/read/board4 headersCORE: READrung tenantgrant readRECORDreads or writesCARD, 200body BoardAnswerThe input is BoardReadInput. Every response carries the contract's hash.flows forwardthe result
The caller sends BoardReadInput to /v1/read/board. The platform returns a card whose body is BoardAnswer.
POST/v1/read/board

Read a board. The call needs the tenant rung under a token with the read grant, and it is served by the platform.

The route takes BoardReadInput and returns a card whose body is BoardAnswer.

Request body#

The request body is BoardReadInput.

fieldtyperequirednote
boardidyes
periodWindowno

Response#

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

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

Example#

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

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

MCP tool#

The MCP tool si.read.board 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/BoardAnswer. The tool’s page describes it.

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

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

Claims#

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