# Rainbrand API > Rainbrand keeps a whole brand current for agents, gives them the guidance and files each task needs, and checks the result. API and MCP plans from $20 a month. Rainbrand builds a brand from your sources (a website, a brand guide, logos, fonts, images or written direction) and keeps it current as you edit it. For each task, an agent or your code asks for a Brief: the guidance and the selected files that task needs. A Review checks the finished work against the brand. Agents reach it over MCP; your code uses the REST API. | | | | --- | --- | | Job | [Agentic brand work](https://brandapis.com/guides/which-brand-api#agentic-brand-work) | | Logos | Yes | | Colours | Yes | | Fonts | Yes | | Guidance | Yes | | Files | Yes | | You send | Your sources for a brand, then a task | | Authentication | API key, or OAuth for connected accounts | | Free tier | 1,000 credits and one new brand, once | | Paid from | $20 a month (Plus) | | MCP server | Yes | | Checked | 2026-11-10 | ## What does Rainbrand return? - **Logos:** Logo files from the brand's own sources, chosen for each task in a Brief, or all of them in the Brand Skill. - **Colours:** The brand's colours are part of its profile, with the rules for using them. - **Fonts:** Font files (such as WOFF2) with rendered specimens, selected for each task. - **Guidance:** Markdown guidance for each task in a Brief (voice, visual rules, claims), and the brand's full guidance in the Brand Skill. - **Files:** Images, video and audio kept in the brand's Brand Library, selected for each task. ## How is it billed? Monthly credits on every plan: a Brief costs 100, a Review 200, a brand edit 300 and a new brand 500. The API and MCP are included in every plan. ## What are the limits? 120 accepted requests per API key, counted until 60 seconds after the last accepted request; 5 new brands per account in any 60 seconds. ## What do the terms require? Not published ## Who keeps it current? You or your customer: describe a change, Rainbrand prepares a brand edit, and you apply or discard it. Briefs requested after that use the new version. ## How do you call it? ``` curl -X POST https://www.rainbrand.com/api/v1/brands -H "x-api-key: $RAINBRAND_API_KEY" -H "Content-Type: application/json" -d '{"sources": [{ "kind": "website", "url": "https://acme.com" }]}' ``` ## When should you use something else? - **For a logo beside a company name**, use a lookup such as [Logo.dev](https://brandapis.com/directory/logo-dev) or [Brandfetch](https://brandapis.com/directory/brandfetch). A new brand in Rainbrand costs 500 credits and has to be analysed before it's ready, so it isn't meant for thousands of CRM rows. - **For the archive, rights and distribution of files**, keep your DAM. Rainbrand doesn't sync with any DAM; its own advice is to add a curated set of current files and leave the rest where it is. - **If your code needs to hear when a brand changes**, no webhooks are documented. Store the brand version you used with each result. ## How do you start? The [API quickstart](https://docs.rainbrand.com/api/quickstart?utm_source=brandapis.com&utm_medium=satellite&utm_campaign=entry-quickstart) adds a brand and requests a Brief in four calls. For agents in Claude, ChatGPT, Cursor or Codex, connect the MCP server at `https://mcp.rainbrand.com/mcp` ([setup](https://docs.rainbrand.com/mcp/getting-started?utm_source=brandapis.com&utm_medium=satellite&utm_campaign=entry-mcp)). ## Sources - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) - (checked 2026-11-10) --- Source: https://brandapis.com/directory/rainbrand Last updated: 2026-11-10 Published by The Brand API Register. The Brand API Register is run by Rainbrand, which makes one of the APIs listed. Its entry follows the same rules as the others.