Customer brands in an AI product
If your product makes work for customers, a lookup gets their logo at signup and an agentic brand API gives each job its guidance and files. What each costs.
Last updated 2026-11-10
If your product makes things for your customers (ads, landing pages, emails, decks), every job needs that customer's brand. A logo and two colours make a first draft look right. The rest decides whether the customer ships it: the voice, the claims they're allowed to make, the product photos to use and the font for the headline.
What does each job need?
- Identity: the logo file for the right background, the colours, the fonts.
- Guidance: the voice, and the rules that apply to this kind of work.
- Files: approved product photos and other material to place, not redraw.
- Currency: when the customer changes something, the next job uses it.
- A check: the finished work compared with the brand before the customer sees it.
Which API gives you which part?
| Need | One-off lookup | Agentic brand API |
|---|---|---|
| Logo and colours at signup | Yes, from their domain | Yes, once their brand is added |
| Voice and rules | A summary of their public site at most (Brandfetch) | Yes, chosen for each job |
| Approved files | Images from their website | Yes, from the files they add |
| Kept current | Re-crawls, owner edits, webhooks | Edits you or they prepare and apply |
| Checks the result | No | Yes |
If a customer keeps their files in a DAM, its API can supply the originals with their permission; see the DAM entries.
A common setup
- At signup, call a lookup with the domain of the customer's work email, so the first screen shows their logo and colours. See prefilling signup from a work email.
- When they start, add their brand to an agentic brand API from their website, brand guide and files.
- For each job, ask for the guidance and files that job needs, generate with your own models, and check the result before showing it.
With Rainbrand, step 2 is one call that creates a brand, and step 3 is a Brief for each piece of work and a Review of the result. Your server uses an API key; if customers connect their own Rainbrand accounts, you use OAuth. Embed Rainbrand into your product covers the setup.
What does it cost per customer and per job?
From the pricing pages, as checked on 10 November 2026:
| Step | Product | Cost |
|---|---|---|
| Logo and colours at signup | Logo.dev Brand API | 5 credits, $0.05 a lookup |
| Logo and colours at signup | Brandfetch Brand API | One brand fetch; $0.10 over the plan |
| A new customer brand | Rainbrand | 500 credits, $1.75 on Pro |
| Guidance and files for one job | Rainbrand Brief | 100 credits, $0.35 on Pro |
| A check of one piece of work | Rainbrand Review | 200 credits, $0.70 on Pro |
Rainbrand's Pro plan is $35 a month for 10,000 credits, which is $0.35 per 100.
What should you check before you build?
- Storage. Logo.dev lets you store what its API returns on every plan. Brandfetch lets you cache Brand API data for 30 days, then refresh or delete it.
- Changes. Brandfetch and Logo.dev send webhooks on paid plans when a brand you follow changes. Rainbrand documents no webhooks, so store the brand version you used with each result.
- Onboarding rate. Rainbrand starts at most 5 new brands per account in any 60 seconds, so queue your onboarding.