200 and a JSON body in one of two shapes. Anything else is treated as a failure (see Status codes, limits, and failures).
Shape 1: an answer
Shape 2: no answer
Use this when the question is outside what your system knows. It is a normal, expected outcome, not an error.Field rules
Validation is strict on the fields above and lenient on everything else. Unknown keys are dropped before the agent sees the response, so you cannot pass extra fields through to the model. A body that fails validation counts as unavailable for that turn.
Product references
Each entry has akind and a value.
References are hints, not commands. The agent resolves each one against the catalog Anagram has synced for your project. A reference that does not resolve (wrong store, unpublished, deleted) is dropped without comment. Prices, stock, images, and titles always come from the catalog, never from your response.
If your guidance points at a category rather than specific SKUs, leave
products empty and describe the criteria in answer. The agent will run a catalog search using those criteria.
Citations
Citations are shown as provenance next to the agent’s reply. Anagram does not fetch, validate, or summarize the linked pages. Point them at public pages a shopper could open.Writing answers that work
The agent readsanswer as advice from a named expert, then decides what to say to the shopper in its own voice. It works best when you:
- Lead with the recommendation, then the reasoning. The first sentence carries the most weight.
- Name the selection criteria (weight range, insulation grade, action, fit) rather than only naming products. Criteria survive when the specific product is out of stock.
- Stay inside the expertise you declared in Studio. If the question drifts into pricing, policy, or something you don’t cover, return
no_answer. - Keep it under a few hundred words. The 10,000-character ceiling is a safety limit, not a target.