Business

For an agent on the company itself. Stating what the company sells and to whom, reading the canvas, ranking leads and researching a market are catalog actions on the Actions lane (`business_read`, `business_update`, `lead_list`, `research_run`); what lives here is the standing guidance they derive under.

Position

The standing frame the project derives under. The write steers what is derived next, without re-deriving from scratch; every read and every derivation runs as a catalog action on the Actions lane.

PUT/v1/gtm/outreach-guidanceAPI key

Steer the guidance

Set the standing guidance every derived recommendation is held to.

Project-wide and standing: it steers what is derived next rather than editing what was derived already, so it is the right place to encode a constraint you never want violated.

Body

Field	Type	Required	Description
guidance	string	required	The standing instruction, in prose.

Request · curl

curl -X PUT "https://runlogai.com/runlogapi/gtm/outreach-guidance" \
  -H "Authorization: Bearer $RUNLOG_API_KEY" \
  -H "X-Project-Id: p7Kd2mQx" \
  -H "Content-Type: application/json" \
  -d '{
  "guidance": "Never open with a discount. Lead with the operational failure the buyer already knows about."
}'

Response · 200

{
  "updated": true
}

Errors

Status	error	When
400	invalid request body	The body is not JSON, or exceeds the 1 MB request-body cap.
403	editor access required	You can read the project but not write to it.
404	project not found	The project does not exist, or you have no access to it. Projects are non-enumerable, so a denied read is indistinguishable from a missing one.
401	invalid API key	The `Authorization` header is missing, malformed, or names a revoked key.
400	name the target project via the X-Project-Id header or projectId query	No project was named and the key is not bound to one.
429	rate limit exceeded	You passed 60 requests/minute on this key. `Retry-After` carries the seconds to wait.
500	internal error	The relay failed to serve the request. Retry with backoff; the cause is logged server-side against your request.