Brand enrichment
Mit Brand-Endpunkten verwandelst du brand enrichment in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Use a Brand Data API to turn any domain into a normalized brand profile — title, description, slogan, brand colors, logos and icons, social profiles, footer links, and schema.org organization data — as structured JSON for enrichment, branding, and research workflows.
Use a Brand Data API to extract a normalized brand profile by domain — title, colors, logos, socials, links, and schema.org org data — as structured JSON.
Endpunkt-Familien
1
Dokumentierte Parameter
6
Beispiele
1
Live-Katalog-Snapshot
Aktive Endpunkte
1
Methoden
GET
Pflichtparameter
2
Schema-Referenzen
1
{
"platform": "Brand",
"endpoint": "brand-retrieve",
"method": "GET",
"path": "/brand/retrieve",
"auth": "apiKey"
}Verwandte Use Cases
Use Cases
Use a Brand Data API to extract a normalized brand profile by domain — title, colors, logos, socials, links, and schema.org org data — as structured JSON.
Mit Brand-Endpunkten verwandelst du brand enrichment in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Brand-Endpunkten verwandelst du logo & color extraction in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Brand-Endpunkten verwandelst du company data enrichment in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Brand-Endpunktkatalog — 1 Endpunkte, 6 dokumentierte Request-Parameter und 1 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
1 documented Brand endpoints, all in the Retrieve family.
6 request parameters are documented across those Brand endpoints, 2 of them required — the full input contract is public before you write any integration code.
1 of the 1 Brand endpoints ship a recorded example response, and 1 carry a documented response schema — you can code against the real JSON before the first request.
Brand endpoints document their error responses (400, 404, 408, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
1 hosted MCP tool backs the Brand endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/brand/retrieve
Endpunktkatalog
/brand/retrieveReturns a brand profile for a domain (title, description, brand colors as hex, logos and icons ranked best-first, backdrops, socials, links, and any schema.org organization data). Enrichment-only fields that are not present in the page markup are returned as null.
MCP-Tool brand_retrieve
Verwandte APIs
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
So scrapst du Brand
Brand data — logo, colors, description, social profiles — is scattered across a company's homepage markup, its Web App Manifest, and its schema.org metadata. The Brand Data API collapses that into one call: pass a domain, get a normalized brand profile.
The endpoint takes a domain and fetches that site's homepage and Web App Manifest.
You get title, description, slogan, brand colors normalized to hex, logos and icons ranked best-first, backdrops, social profiles, footer links, and any schema.org organization data.
Enrichment-only fields that are not present in the page markup come back as null rather than guessed, so a missing logo is a real signal and not a silent failure.
force_language, maxSpeed, maxAgeMs, and timeoutMS control the language, how aggressively the page is fetched, how stale a cached result may be, and when to give up.
FAQ
Title, description, slogan, brand colors normalized to hex, logos and icons ranked best-first, backdrops, social profiles, footer links, and any schema.org organization data — extracted from the homepage and the Web App Manifest in a single call.
The field comes back null. Enrichment-only fields absent from the page markup are returned as null rather than inferred, so you can tell a brand with no manifest icon apart from a call that failed to look.
Yes, and that is the common use. One call per domain returns a consistent profile shape, so a list of company domains becomes a table of names, descriptions, logos, colors, and social links without per-site parsing.