Docs / Reference / ask: keep question

ask: keep question.

The question and its scope to a saved question

Figure 1POST /v1/ask/keep_questionspecified

The caller sends KeepQuestionInput to /v1/ask/keep_question. The platform returns a card whose body is SavedQuestion.

POST/v1/ask/keep_question

Keep a question. The call needs the user rung under a token with the ask grant, and it is served by either, by the size bound.

The route takes KeepQuestionInput and returns a card whose body is SavedQuestion.

Request body#

The request body is KeepQuestionInput.

field	type	required	note
`question`	SavedQuestion	yes

Response#

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

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/ask/keep_question \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "question": { "name": "…", "over": "stocks", "query": null, "scope": { "level": "shared" } } }'

import { client } from "@scale/sdk";
const answer = await client.ask.keep_question({
    "question": {
      "name": "…",
      "over": "stocks",
      "query": null,
      "scope": {
        "level": "shared"
      }
    }
  });
// answer.body is a SavedQuestion. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/ask/keep_question",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "question": {
        "name": "…",
        "over": "stocks",
        "query": null,
        "scope": {
          "level": "shared"
        }
      }
    }).json()

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

MCP tool#

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

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

{
  "question": {
    "name": "…",
    "over": "stocks",
    "query": null,
    "scope": {
      "level": "shared"
    }
  }
}

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

Claims#

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