> ## Documentation Index
> Fetch the complete documentation index at: https://docs.url2llm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Branding

> Extract the visual identity visible on a rendered public page.

Request `branding` from a scrape to read the visual identity expressed by that page. Browser rendering must be enabled. The output is included in the same page request with no current format surcharge.

```json theme={null}
{
  "url": "https://example.com",
  "formats": { "branding": true, "screenshot": true },
  "renderJs": true
}
```

Read the kit from `data.branding` and compare it with `data.screenshot` when checking the visual result.

## What the kit contains

| Section | What it describes |
| - | - |
| `colors` | Action, heading, body, surface, accent, and link color roles |
| `fonts` | Heading and body font families |
| `typography` | Heading and body family, fallback, weight, case, and size |
| `spacing` | A detected base spacing unit and common border radius |
| `components` | Styles of the primary button, secondary button, and input |
| `logo` | Primary logo and favicon URLs when available |

The implemented API reference defines the nested response fields. These sections report signals found on the rendered page. A role with no reliable signal stays `null`; a missing value does not mean the brand has no such color, font, or component.

## Pick a representative page

Start with the homepage or a public product page that shows the site's usual headings, buttons, inputs, and logo. A sparse error page or login screen may show a different visual identity.

Branding describes one captured page. It is not a merged domain-wide brand profile, company database record, or generated brand guideline document. To compare several pages, scrape them individually and decide how your application reconciles their kits.

## Keep source context

Store the source URL, final URL, and your own capture timestamp beside the kit. If mobile, country, language, or source changes matter to your workflow, keep those request settings too. The same site can use different component or font styles across pages.

Logo URLs point to discovered assets. Your application decides whether to fetch and store those assets. An unavailable logo can be `null`; do not substitute unrelated page images automatically.

Use the [Brand Playground](https://url2llm.com/dashboard/playground/brand) as an organization admin to inspect a kit before integrating it. See [browser settings](https://docs.url2llm.com/guides/browser-rendering.md) for capture options and [links and assets](https://docs.url2llm.com/features/links-assets.md) for other page media.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.