ask: saved view.

The view. Or the view and a caller to the definition. Or its rows, with when they were built

Request body#

The request body is SavedViewInput.

Response#

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

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

Example#

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

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

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

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

MCP tool#

The MCP tool si.ask.saved_view 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/SavedViewAnswer. The tool’s page describes it.

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

{}