How is this different from colors only?

Styleguide extraction walks the design system surface — typography, spacing cues, and repeated component patterns — not just hex codes.

Is this the same as your Logo Link CDN?

Brand retrieval returns structured JSON (logos, colors, metadata). Logo Link is optimized for instant image delivery at the edge.

How fresh is the data?

Responses are cached with tiered TTLs; you can prefetch or refresh when you need the latest crawl.

Do you return multiple logo variants?

Yes — SVG when available, raster fallbacks, and type hints so you can pick the right asset for light and dark UI.

BRAND DATA

The brand book,
in JSON.

The complete visual system: colors, fonts, spacing, iconography, and component patterns — built for programmatic theming.

Try the endpoint Read the docs

https://

Extract colors, typography, and UI tokens from a site.

Start free, no card required, most teams ship a first integration in under ten minutes.

Why this endpoint exists

Not another JSON page.
A production workflow in one call

One call in. Tokens you can compile out.

Without Orsa

Before Orsa

A browser worker, proxy account, parser, retry queue, and schema contract for one endpoint.
Product teams wait while platform teams debug website-specific failures.
Every new data field becomes another brittle scraper branch.

With Orsa

After Orsa

One call in. Tokens you can compile out. With retries, rendering, and validation handled behind the API.
The response shape is typed, documented, and ready for product code.
Teams combine it with adjacent Orsa endpoints without adding vendors.

How it works

Teach the workflow,
then show the endpoint

Point Orsa at a domain, let the platform handle the web work, and receive a response your product can trust.

Input01

Send a domain

apple.com

Orsa runtime02

Render, retry, enrich

Orsa handles browser execution, proxy escalation, parsing, validation, caching, and typed response shaping behind the API.

Output03

One call in. Tokens you can compile out.

Use the result in white-label saas without owning the extraction stack.

REST path: /api/v1/brand/styleguideSame endpoint used by the SDK examples below.
Input shape: domainapple.com
SDKs: TypeScript, Python, cURLStart with TypeScript, Python, or direct cURL.
Best first use: White-label SaaSSkin customer portals with their real design language.

Production numbers

Performance your product
can actually plan around

Every endpoint page should answer the practical buying question: will this hold up once it leaves the demo?

p50 latency1.8sMeasured as production API latency, not a static mock.

p99 latency6.2sBuilt for the long tail of real websites and crawler paths.

quality barDeep extraction — richer than a single-page palette passDeep extraction — richer than a single-page palette pass

credits per call1 keySelf-serve usage with predictable metering and no scraping infrastructure to own.

Feature layer

More than the response.
The operating layer behind it

Stripe pages teach the system around the API: inputs, retries, observability, adjacent products, and the code path. This section does the same for Orsa endpoints.

Typed response contracts for product code and AI tools.
Browser, proxy, cache, and validation logic handled by Orsa.
Direct fit for white-label saas and design ops.

Endpoint

/api/v1/brand/styleguide

Example input

apple.com

Promise

One call in. Tokens you can compile out.

Pairs with

Company Fonts, Company Colors, Website Screenshot

Built for the job

What teams ship with
the brand book, in json.

Each product page now speaks to the real workflow behind the endpoint, with concrete jobs instead of a generic feature list.

White-label SaaS

Skin customer portals with their real design language.

Design ops

Diff styleguides when customers rebrand overnight.

AI theming

Let agents reason over tokens instead of screenshots alone.

Implementation

Keep the code small.
Let Orsa do the messy part

Use the endpoint directly, then combine it with adjacent Orsa APIs as the workflow grows.

Get an API key API reference

request

Responsetyped json

{
  "domain": "apple.com",
  "styleguide": {
    "colors": { "primary": "#0071E3" },
    "typography": { "display": "SF Pro Display" }
  }
}

Combine with

Build the full workflow,
not another point solution

The best product integrations usually combine two or three Orsa endpoints behind one customer experience.

Company Fonts Company Colors Website Screenshot

FAQ

The questions teams ask
before shipping

Short answers for the practical details: rendering, limits, freshness, and how this fits into production.

Get started

Put this endpoint
in your product today

Try the live endpoint, then wire the same response into your app with one API key.

Try this endpoint

One API key for every Orsa endpoint · No card required to start.

More than the response.
The operating layer behind it

Stripe pages teach the system around the API: inputs, retries, observability, adjacent products, and the code path. This section does the same for Orsa endpoints.

Typed response contracts for product code and AI tools.

Browser, proxy, cache, and validation logic handled by Orsa.

Direct fit for white-label saas and design ops.

The brand book,in JSON.

Not another JSON page.A production workflow in one call

Before Orsa

After Orsa

Teach the workflow,then show the endpoint

Send a domain

Render, retry, enrich

One call in. Tokens you can compile out.

Performance your productcan actually plan around

More than the response.The operating layer behind it

What teams ship withthe brand book, in json.

White-label SaaS

Design ops

AI theming

Keep the code small.Let Orsa do the messy part

Build the full workflow,not another point solution

The questions teams askbefore shipping

Put this endpointin your product today

The brand book,in JSON.

Not another JSON page.A production workflow in one call

Before Orsa

After Orsa

Teach the workflow,then show the endpoint

Send a domain

Render, retry, enrich

One call in. Tokens you can compile out.

Performance your productcan actually plan around

More than the response.The operating layer behind it

What teams ship withthe brand book, in json.

White-label SaaS

Design ops

AI theming

Keep the code small.Let Orsa do the messy part

Build the full workflow,not another point solution

The questions teams askbefore shipping

Put this endpointin your product today

The brand book,
in JSON.

Not another JSON page.
A production workflow in one call

Teach the workflow,
then show the endpoint

Performance your product
can actually plan around

More than the response.
The operating layer behind it

What teams ship with
the brand book, in json.

Keep the code small.
Let Orsa do the messy part

Build the full workflow,
not another point solution

The questions teams ask
before shipping

Put this endpoint
in your product today

The brand book,
in JSON.

Not another JSON page.
A production workflow in one call

Teach the workflow,
then show the endpoint

Performance your product
can actually plan around

More than the response.
The operating layer behind it

What teams ship with
the brand book, in json.

Keep the code small.
Let Orsa do the messy part

Build the full workflow,
not another point solution

The questions teams ask
before shipping

Put this endpoint
in your product today