Docs / Reference / read: fit plays

read: fit plays.

Reads the tactics that fit one phase of the search, for a vertical or a kind of offering to The answer gives the tactics in the order to run them

Figure 1POST /v1/read/fit_playsspecified

The caller sends FitPlaysInput to /v1/read/fit_plays. The platform returns a card whose body is [Tactic].

POST/v1/read/fit_plays

Read the tactics of a phase. The call needs the tenant rung under a token with the read grant, and it is served by either, by the size bound.

The route takes FitPlaysInput and returns a card whose body is Tactic.

Request body#

The request body is FitPlaysInput.

field	type	required
`phase`	`one of find the market \| sculpt the offering \| test the fit \| build a beachhead \| engineer demand \| find demand \| grow in a market \| hedge`	yes
`vertical`	`id`	no
`kind_of_offering`	KindOfOffering	no

Response#

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

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/read/fit_plays \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "phase": "find the market" }'

import { client } from "@scale/sdk";
const answer = await client.read.fit_plays({
    "phase": "find the market"
  });
// answer.body is a [Tactic]. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/read/fit_plays",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "phase": "find the market"
    }).json()

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

MCP tool#

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

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

{
  "phase": "find the market"
}

Without a key, this page shows the request only. The request body is FitPlaysInput, and the route returns a card whose body is [Tactic].

Claims#

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