What Henry does

Henry is the team-facing read-only AI assistant in Brand Atlas. It answers questions about the brand record for whoever has the right to read it. Henry does not edit. Henry is available on Keeper and Guardian. It uses an OpenAI or Gemini API key the customer supplies; the customer pays the AI provider directly for usage.

​

What Henry can do

Five capabilities, in order of how often they are used:

1. Answer questions about the brand record. What is our secondary blue’s Pantone match? Which weights of our headline typeface are licensed? What are our rules for photographing people?
2. Summarise sections. Give me a 100-word summary of the Voice section for an intro briefing.
3. Translate questions into search. Where do we cover sub-brand lock-ups? Henry surfaces the right section without needing the team member to know the section name.
4. Find precedents. Have we documented a rule for this kind of partnership before? Henry searches the brand record and the Update Request history.
5. Explain owned vocabulary. Henry uses the Glossary as its primary source for brand terms. What is brand-on-course? returns the canonical definition.

​

What Henry cannot do

Five hard limits:

1. Edit the brand record. Henry is read-only. To change anything, the team raises an Update Request; the brand owner decides.
2. Read material the user cannot read. Henry’s read access is scoped by the user’s role. A team member talking to Henry cannot get Henry to surface a restricted Horizon.
3. Take actions outside answering. Henry does not send emails, post to channels, create Guest Passes, or run any other portal action.
4. Remember between sessions. Each Henry session is fresh. Long-term continuity lives in the brand record, not in Henry’s memory.
5. Generate images, video, or files. Henry produces text. Other generation tools live outside Brand Atlas.

​

Where Henry appears

Henry is visible as a chat icon in the bottom-right corner of every page in the atlas, for every user who has Henry available. Clicking the icon opens a conversation panel. The team member can:

• Ask any question about the brand record.
• Drop a copy block or paste a quote from a draft and ask Henry to check it against the rules.
• Ask Henry to find where something is documented (faster than search for many questions).

Henry’s responses include citations: the section, the line, or the Update Request the answer is drawn from. Citations make Henry’s answers traceable.

​

Who pays for Henry

The customer pays the AI provider (OpenAI or Gemini) directly, at the provider’s usage rates. Brand Atlas does not mark up the AI usage; Brand Atlas’s revenue is the Keeper or Guardian subscription. In practice, most teams find their Henry usage costs tens of dollars per month at most. A heavy-use team running Henry across a large marketing organisation may see usage closer to a hundred dollars. The exact cost depends on the team’s behaviour and the provider’s current rates. The BYOK model has three consequences:

• The Keeper subscription stays flat at $79/mo regardless of Henry usage.
• The customer controls their own usage cap with their provider.
• The customer’s contractual relationship for the AI usage is with the provider, not with Brand Atlas. Brand Atlas mediates the integration; the bill is provider-to-customer.

​

Setting up Henry

The setup is described in Setting up Henry. The short version: open Settings → AI → Henry, choose OpenAI or Gemini, paste an API key, confirm. Henry is available immediately. Setup takes about five minutes including the time to create the API key in the provider’s dashboard.

​

What the AI provider sees

When a team member talks to Henry:

• The team member’s prompt is sent to the provider.
• The relevant brand-record context is sent as grounding.
• The provider returns the response.
• Brand Atlas presents the response to the team member.

The provider’s enterprise API tier does not use API content for training. The full disclosure is in How your key is stored and BYOK Policy. What the provider sees:

• The team member’s prompts.
• The brand-record context relevant to those prompts.
• The customer’s account identifier (the API key).

What the provider does not see:

• The customer’s identity beyond what the API key implies.
• Other atlases (each atlas is isolated).
• The team member’s identity in Brand Atlas terms (only that a session is in progress).

​

Choosing between OpenAI and Gemini

Both providers work. The choice depends on:

• Existing relationships. If the customer already has an OpenAI or Gemini account, use the existing one.
• Cost preferences. Pricing varies by provider and by current rates. Compare on the providers’ pricing pages.
• Compliance requirements. Some customers have requirements that favour one provider.
• Performance. Both are competent; light differences in response style. Either is fine.

Switching providers later is straightforward; see Switching providers.

​

What Henry is not

Three things Henry is not, to head off confusion:

• A general-purpose AI assistant. Henry is bounded to the brand record. Ask Henry about your tax return and Henry will explain that the question is outside scope.
• A customer service bot for Brand Atlas. Henry serves the customer’s team in the customer’s atlas. Questions about Brand Atlas itself go to support, not to Henry.
• A replacement for the team’s expertise. Henry surfaces what is documented. The team’s own knowledge is what gets documented in the first place.

​

Related pages