session: sign in.

Nothing, or the tenant to sign in to to the way the browser was opened, then the caller as a view once the code came back; the refresh token goes to the keychain and never to the caller

Request body#

The request body is SignInInput.

Response#

The route returns a card whose body is Caller. 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 user rung and a token with the read grant. The desktop app serves this route.

Example#

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

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

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

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

MCP tool#

The MCP tool si.session.sign_in 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/Caller. The tool’s page describes it.

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

{}