auto_write

Pass the merchant's direction to the Brain. Use `add_instruction` when they state a standing goal or guardrail ("stop di

Pass the merchant's direction to the Brain. Use add_instruction when they state a standing goal or guardrail ("stop discounting", "focus on the winter range", "never advertise brand X", "keep spend under 40 a day") — the Brain reads these on every cycle and treats a guardrail as a hard constraint that overrides its own judgement. Use remove_instruction with the EXACT wording of an existing one when they retract it; call get_brain_thinking first and read the list back to them. Use note for a one-off fact the next cycle should know ("we are out of stock on the Aurelle line until Friday") that should not become a permanent rule. ALWAYS confirm the wording with the merchant before writing it — this changes what an autonomous system does with their money. It cannot change budgets, modes, autonomy or caps, and it cannot approve or dispatch anything.

post/api/v1/tools/tell_brain

Request

  • Base URL: https://app.magistry.io
  • URL: https://app.magistry.io/api/v1/tools/tell_brain
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL https://app.magistry.io/api/oauth/authorize, token URL https://app.magistry.io/api/oauth/token, scopes: write)

Request body

action'add_instruction' | 'remove_instruction' | 'note' required

add_instruction: a standing rule. remove_instruction: retract one, exact wording. note: a one-off fact for the next cycle only.

textstring required

One line, in the merchant's own words where possible. For remove_instruction, the wording of the existing instruction as get_brain_thinking returned it.

becausestring

Short context: what the merchant said that led to this.

Response

Tool result

okboolean required
resultunknown required

Changes

No recorded changes to this operation across all 3 revisions of this API.