Docs / Reference / act: record fit reading

act: record fit reading.

Records one result of a person's own test: the tactic, the market, the measure, its value, the sample and where it came from to The answer gives the reading as a fact the record keeps

Figure 1POST /v1/act/record_fit_readingspecified

The caller sends FitReadingInput to /v1/act/record_fit_reading. The platform returns a card whose body is FitReading.

POST/v1/act/record_fit_reading

Record a fit reading. The call needs the brand rung under a token with the act grant, and it is served by the platform.

The route takes FitReadingInput and returns a card whose body is FitReading.

Request body#

The request body is FitReadingInput.

field	type	required	note
`tactic`	Tactic	yes
`vertical`	`id`	yes
`segment`	`id`	no
`offering`	`id`	no
`measure`	KindOfMeasure	yes
`value`	`json`	yes	the number, or never measured with the reason
`sample`	`count`	no
`source`	`one of a form \| a CRM \| a capture \| an upload \| a call \| the record`	yes
`hypothesis`	`id`	no
`note`	`text`	no

Response#

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

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/act/record_fit_reading \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "tactic": "…", "vertical": "…", "measure": "…", "value": null, "source": "a form" }'

import { client } from "@scale/sdk";
const answer = await client.act.record_fit_reading({
    "tactic": "…",
    "vertical": "…",
    "measure": "…",
    "value": null,
    "source": "a form"
  });
// answer.body is a FitReading. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/record_fit_reading",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "tactic": "…",
      "vertical": "…",
      "measure": "…",
      "value": null,
      "source": "a form"
    }).json()

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

MCP tool#

The MCP tool si.act.record_fit_reading takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/FitReading. The tool’s page describes it.

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

{
  "tactic": "…",
  "vertical": "…",
  "measure": "…",
  "value": null,
  "source": "a form"
}

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

Claims#

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