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.

How does usage scale for this endpoint?

Crawl jobs grow with pages discovered; single-call endpoints are one request. See the API reference for request semantics.

COMPANY PROFILE

Every official profile.
One response.

Twitter, LinkedIn, GitHub, Instagram, YouTube, TikTok, and more — official handles surfaced from the site graph.

Try the endpoint Read the docs

https://

Retrieve logos, colors, and company metadata from any domain.

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. Typed social links 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. Typed social links 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

vercel.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. Typed social links out.

Use the result in trust panels without owning the extraction stack.

REST path: /api/v1/brand/retrieveSame endpoint used by the SDK examples below.
Input shape: domainvercel.com
SDKs: TypeScript, Python, cURLStart with TypeScript, Python, or direct cURL.
Best first use: Trust panelsShow users where to verify announcements and releases.

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 latency142msMeasured as production API latency, not a static mock.

p99 latency1.1sBuilt for the long tail of real websites and crawler paths.

quality barOfficial profiles prioritized over third-party guessesOfficial profiles prioritized over third-party guesses

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 trust panels and support routing.

Endpoint

/api/v1/brand/retrieve

Example input

vercel.com

Promise

One call in. Typed social links out.

Pairs with

Company Logos, Company Description, Website Screenshot

Built for the job

What teams ship with
every official profile. one response.

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

Trust panels

Show users where to verify announcements and releases.

Support routing

Jump to the right official channel faster.

Graph building

Seed entity graphs with canonical social endpoints.

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": "vercel.com",
  "social_links": {
    "twitter": "https://twitter.com/vercel",
    "github": "https://github.com/vercel",
    "linkedin": "https://linkedin.com/company/vercel"
  }
}

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 Logos Company Description 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 trust panels and support routing.

Every official profile.One response.

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. Typed social links out.

Performance your productcan actually plan around

More than the response.The operating layer behind it

What teams ship withevery official profile. one response.

Trust panels

Support routing

Graph building

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

Every official profile.One response.

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. Typed social links out.

Performance your productcan actually plan around

More than the response.The operating layer behind it

What teams ship withevery official profile. one response.

Trust panels

Support routing

Graph building

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

Every official profile.
One response.

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
every official profile. one response.

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

Every official profile.
One response.

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
every official profile. one response.

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