Scale Intelligence■ Docs
Docs / Reference / read: propensity

read: propensity.

A lead, a move or a play, and which faces, actors or content or both (`PropensityInput`) to every eligible actor and every fitting content with the chance, its interval, its basis and the policy's odds, and the one the policy would choose (`PropensityAnswer`)

Figure 1POST /v1/read/propensityspecified
CALLERyour app or an agentholds the keyAPI GATEWAY/v1/read/propensity4 headersCORE: READrung strategygrant readRECORDreads or writesCARD, 200body PropensityAnswerThe input is PropensityInput. Every response carries the contract's hash.flows forwardthe result
The caller sends PropensityInput to /v1/read/propensity. The platform returns a card whose body is PropensityAnswer.
POST/v1/read/propensity

Read who and what fits a lead. The call needs the strategy rung under a token with the read grant, and it is served by the platform.

The route takes PropensityInput and returns a card whose body is PropensityAnswer.

Request body#

The request body is PropensityInput.

fieldtyperequirednote
leadidyes
moveidno
playidno
faces[one of actor | content]yes

Response#

The route returns a card whose body is PropensityAnswer. 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 strategy rung and a token with the read grant. The platform serves this route.

Example#

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

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

MCP tool#

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

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

{
  "lead": "…",
  "faces": []
}
Without a key, this page shows the request only. The request body is PropensityInput, and the route returns a card whose body is PropensityAnswer.

Claims#

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