brand_playbook

Call brand_playbook.run

'make us a logo', 'make the icon set from our logo', 'make some poses of Alex' — run one of this workspace's brand playbooks: poses of one of the brand's people, a logo pack (a logo with its favicon and icon set), or the icon set from the logo the brand has. It answers in two calls: without confirmation_id it returns the price per stage and a confirmation_id and spends nothing; the same call again with that confirmation_id, on a member's own API key, starts the run, spends the quoted credits and answers its job_run_id. The logo pack pauses after drawing its directions: a call without confirmation_id then answers awaiting_pick, and choosing one (pick) takes the same two calls and spends nothing. Not for a single picture or an edit to one — that is images.generate.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/brand_playbook.run

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/brand_playbook.run
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

key'pose_pack' | 'logo_pack' | 'icon_set' required
inputsobject
confirmation_idstring uuid
workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

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