Docs / Reference / work: search fit

work: search fit.

Searches for product-market fit from one end: an offering looking for its markets, or a concept looking for a market to The call returns the search as work, then the frame that holds what it settled

Figure 1POST /v1/work/search_fitspecified

The caller sends FitSearchInput to /v1/work/search_fit. The platform returns a card whose body is FitSearch.

POST/v1/work/search_fita task, 202

Search for product-market fit. The call needs the brand rung under a token with the work grant, and it is served by the platform.

The route takes FitSearchInput and returns a card whose body is FitSearch.

Request body#

The request body is FitSearchInput.

field	type	required
`brand`	`id`	yes
`from_end`	`one of an offering \| a concept`	yes
`offerings`	`[id]`	yes
`concept`	`text`	no
`candidate_verticals`	`[id]`	yes

Response#

The route returns a card whose body is FitSearch. 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. This route runs as a long step and returns a task with status 202. POST /v1/work/status returns the task’s progress, and POST /v1/work/cancel stops the task.

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 work grant. The platform serves this route.

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/work/search_fit \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "brand": "…", "from_end": "an offering", "offerings": [], "candidate_verticals": [] }'

import { client } from "@scale/sdk";
const answer = await client.work.search_fit({
    "brand": "…",
    "from_end": "an offering",
    "offerings": [],
    "candidate_verticals": []
  });
// answer.body is a FitSearch. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/work/search_fit",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "brand": "…",
      "from_end": "an offering",
      "offerings": [],
      "candidate_verticals": []
    }).json()

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

MCP tool#

The MCP tool si.work.search_fit 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/FitSearch. The tool’s page describes it.

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

{
  "brand": "…",
  "from_end": "an offering",
  "offerings": [],
  "candidate_verticals": []
}

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

Claims#

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