Docs / Reference / read: instruction set

read: instruction set.

Nothing to the set at its current version, assembled

Figure 1POST /v1/read/instruction_setspecified

The caller sends Nothing to /v1/read/instruction_set. The platform returns a card whose body is InstructionSet.

POST/v1/read/instruction_set

Read the research instruction set. The call needs the user rung under a token with the read grant, and it is served by either, by the size bound.

The route takes an empty body and returns a card whose body is InstructionSet.

Request body#

The request body is empty.

Response#

The route returns a card whose body is InstructionSet. 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 or the desktop app serves this route.

Example#

The example sends an empty body.

Example

curl -X POST https://api.scaleintelligence.co/v1/read/instruction_set \
  -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.read.instruction_set({});
// answer.body is a InstructionSet. answer.foot holds the basis, the scope and the time.

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

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

MCP tool#

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

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

{}

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

Claims#

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