curl --request GET \
--url https://api.brandfetch.io/v2/context/{domain} \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.brandfetch.io/v2/context/{domain}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.brandfetch.io/v2/context/{domain}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.brandfetch.io/v2/context/{domain}",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"net/http"
"io"
)
func main() {
url := "https://api.brandfetch.io/v2/context/{domain}"
req, _ := http.NewRequest("GET", url, nil)
req.Header.Add("Authorization", "Bearer <token>")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.get("https://api.brandfetch.io/v2/context/{domain}")
.header("Authorization", "Bearer <token>")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.brandfetch.io/v2/context/{domain}")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'
response = http.request(request)
puts response.read_body{
"meta": {
"domain": "stripe.com",
"canonical_name": "Stripe",
"resolved_at": "2026-10-16T11:00:22.694653+00:00"
},
"identity": {
"tagline": "Financial infrastructure to grow your revenue.",
"mission": "Stripe builds programmable financial infrastructure to make financial services easier and cheaper for businesses to start, operate, and scale.",
"description": "Stripe is a financial technology company founded in 2010 by brothers Patrick and John Collison and headquartered in South San Francisco, California; it provides payments processing, billing, and money-movement infrastructure to more than 5 million businesses, from solo founders to global enterprises. Its programmable APIs, broad international payment support, and integrated fraud and risk tools let businesses assemble financial services around their own models.",
"tags": [
"online payment processing",
"subscription billing infrastructure",
"marketplace payments and payouts",
"embedded business finance APIs",
"payment fraud prevention"
]
},
"positioning": {
"value_proposition": "Stripe turns payments, billing, and money movement into programmable infrastructure, letting businesses assemble the financial systems their model needs on one platform rather than stitch together separate providers. Its payment network’s transaction data continuously improves acceptance and fraud decisions, helping companies grow across markets while reducing the engineering and operational work of running commerce.",
"target_audience": [
{
"segment": "Founders and operators at startups and small businesses selling online",
"description": "Entrepreneurs launching or scaling digital businesses use Stripe Checkout, Payment Links, and billing tools to start taking payments without building a payments stack from scratch."
},
{
"segment": "Finance, payments, and engineering teams at large international enterprises",
"description": "Teams managing high transaction volumes and cross-border expansion use Stripe’s global payment processing, authorization optimization, fraud controls, and custom pricing to improve acceptance and consolidate infrastructure."
},
{
"segment": "Platforms, marketplaces, and software companies embedding financial services",
"description": "Product and engineering teams serving merchants, workers, or end users use Stripe Connect and related APIs to onboard sellers, route payments, manage payouts, and build embedded payment or financial products."
}
],
"products_and_services": [
{
"name": "Payments",
"type": "service",
"description": "A payment processing service for businesses that accepts cards, digital wallets, and local payment methods online and in person, with support for more than 135 currencies and payment methods.",
"category": "payment processing",
"features": [
"Accept online payments",
"Take in-person payments",
"Offer local payment methods"
],
"tags": [
"payments",
"checkout",
"global"
],
"url": "https://stripe.com/pricing",
"pricing": {
"model": "usage_based",
"free_tier": null,
"starting_price": null,
"currency": null,
"unit": null,
"plans": null,
"url": "https://stripe.com/pricing"
}
},
{
"name": "Billing",
"type": "service",
"description": "A recurring billing and subscription management service that lets businesses charge customers using flat-rate, per-seat, or usage-based models and manages more than 200 million active subscriptions.",
"category": "billing software",
"features": [
"Create subscription plans",
"Charge for usage",
"Manage recurring subscriptions"
],
"tags": [
"subscriptions",
"invoicing",
"usage_based"
],
"url": null,
"pricing": null
},
{
"name": "Terminal",
"type": "product",
"description": "A set of tools for businesses to accept in-person payments through Stripe, including card-present checkout that can be coordinated with online payments.",
"category": "point-of-sale payments",
"features": [
"Accept in-person card payments",
"Unify online and in-person payments"
],
"tags": [
"in_person",
"point_of_sale",
"payments"
],
"url": null,
"pricing": null
}
]
},
"brand": {
"voice": {
"summary": "Stripe speaks with an assured, intellectually ambitious business voice, addressing companies directly while grounding big economic ideas in practical outcomes. Its copy pairs concise product-led claims with precise metrics and technical explanations; the About page’s phrase “improving the conditions for economic growth and prosperity” captures its recurring focus on growth, infrastructure, and scale.",
"attributes": [
"measured",
"ambitious",
"technical",
"precise"
],
"avoid": [
"breathless hype",
"folksy banter"
]
},
"style": {
"summary": "Stripe’s lowercase “stripe” wordmark is a compact, bold sans-serif logotype, distinctive for its clean, unadorned letterforms rather than a separate emblem. The visual system pairs crisp geometric sans typography with a predominantly white canvas, deep navy and blue-gray text, vivid violet accents, and expressive gradients or abstract flowing color forms, balanced by spacious layouts and restrained product imagery.",
"attributes": [
"minimal",
"geometric",
"editorial",
"bold",
"polished"
]
}
},
"competition": {
"competitors": [
{
"name": "Adyen",
"domain": "adyen.com",
"type": "direct",
"category": "payment processing",
"positioning": "Enterprise-focused global payments platform with a unified commerce offering.",
"overlap": [
"Online card processing and local payment methods",
"In-person payments through point-of-sale terminals",
"Enterprise merchants and global payment operations"
]
},
{
"name": "PayPal",
"domain": "paypal.com",
"type": "direct",
"category": "payment processing",
"positioning": "Consumer-recognized wallet and merchant payments provider with broad online checkout adoption.",
"overlap": [
"Online payment acceptance for businesses",
"Digital wallet checkout",
"Small-business and enterprise merchant services"
]
},
{
"name": "Checkout.com",
"domain": "checkout.com",
"type": "direct",
"category": "payment processing",
"positioning": "Enterprise-oriented payment processor focused on digital businesses and global scale.",
"overlap": [
"Online payment processing",
"Global acquiring and local payment methods",
"Large digital merchants"
]
}
]
}
}{
"message": "Bad Request"
}{
"message": "Unauthorized"
}{
"message": "Payment required. Either authenticate with a Brandfetch API key (Authorization: Bearer <key>) or pay for this request with x402: sign the payment described in the PAYMENT-REQUIRED header and retry with a PAYMENT-SIGNATURE header.",
"documentation": "https://docs.brandfetch.com/agents/pay-per-request",
"pricing": {
"route": "GET /v2/brands/*",
"price": "$0.10"
},
"resource": "https://api.brandfetch.io/v2/brands/nike.com",
"standingAccess": "For many requests, POST /v2/agents/access (paid the same way) provisions an API key preloaded with prepaid credits."
}{
"message": "<Not Found> or <Invalid Domain Name>"
}{
"message": "We couldn't read this domain (the site appears to block automated requests)."
}{
"message": "API key quota exceeded"
}{
"message": "The brand context for this domain is still being generated. Retry in 30 seconds."
}Brand Context API reference
Get a structured brand context for a domain with GET /v2/context/, covering identity, positioning, products, voice, style, and competitors, as JSON or Markdown.
curl --request GET \
--url https://api.brandfetch.io/v2/context/{domain} \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.brandfetch.io/v2/context/{domain}"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.brandfetch.io/v2/context/{domain}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.brandfetch.io/v2/context/{domain}",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
CURLOPT_HTTPHEADER => [
"Authorization: Bearer <token>"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}package main
import (
"fmt"
"net/http"
"io"
)
func main() {
url := "https://api.brandfetch.io/v2/context/{domain}"
req, _ := http.NewRequest("GET", url, nil)
req.Header.Add("Authorization", "Bearer <token>")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))
}HttpResponse<String> response = Unirest.get("https://api.brandfetch.io/v2/context/{domain}")
.header("Authorization", "Bearer <token>")
.asString();require 'uri'
require 'net/http'
url = URI("https://api.brandfetch.io/v2/context/{domain}")
http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true
request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'
response = http.request(request)
puts response.read_body{
"meta": {
"domain": "stripe.com",
"canonical_name": "Stripe",
"resolved_at": "2026-10-16T11:00:22.694653+00:00"
},
"identity": {
"tagline": "Financial infrastructure to grow your revenue.",
"mission": "Stripe builds programmable financial infrastructure to make financial services easier and cheaper for businesses to start, operate, and scale.",
"description": "Stripe is a financial technology company founded in 2010 by brothers Patrick and John Collison and headquartered in South San Francisco, California; it provides payments processing, billing, and money-movement infrastructure to more than 5 million businesses, from solo founders to global enterprises. Its programmable APIs, broad international payment support, and integrated fraud and risk tools let businesses assemble financial services around their own models.",
"tags": [
"online payment processing",
"subscription billing infrastructure",
"marketplace payments and payouts",
"embedded business finance APIs",
"payment fraud prevention"
]
},
"positioning": {
"value_proposition": "Stripe turns payments, billing, and money movement into programmable infrastructure, letting businesses assemble the financial systems their model needs on one platform rather than stitch together separate providers. Its payment network’s transaction data continuously improves acceptance and fraud decisions, helping companies grow across markets while reducing the engineering and operational work of running commerce.",
"target_audience": [
{
"segment": "Founders and operators at startups and small businesses selling online",
"description": "Entrepreneurs launching or scaling digital businesses use Stripe Checkout, Payment Links, and billing tools to start taking payments without building a payments stack from scratch."
},
{
"segment": "Finance, payments, and engineering teams at large international enterprises",
"description": "Teams managing high transaction volumes and cross-border expansion use Stripe’s global payment processing, authorization optimization, fraud controls, and custom pricing to improve acceptance and consolidate infrastructure."
},
{
"segment": "Platforms, marketplaces, and software companies embedding financial services",
"description": "Product and engineering teams serving merchants, workers, or end users use Stripe Connect and related APIs to onboard sellers, route payments, manage payouts, and build embedded payment or financial products."
}
],
"products_and_services": [
{
"name": "Payments",
"type": "service",
"description": "A payment processing service for businesses that accepts cards, digital wallets, and local payment methods online and in person, with support for more than 135 currencies and payment methods.",
"category": "payment processing",
"features": [
"Accept online payments",
"Take in-person payments",
"Offer local payment methods"
],
"tags": [
"payments",
"checkout",
"global"
],
"url": "https://stripe.com/pricing",
"pricing": {
"model": "usage_based",
"free_tier": null,
"starting_price": null,
"currency": null,
"unit": null,
"plans": null,
"url": "https://stripe.com/pricing"
}
},
{
"name": "Billing",
"type": "service",
"description": "A recurring billing and subscription management service that lets businesses charge customers using flat-rate, per-seat, or usage-based models and manages more than 200 million active subscriptions.",
"category": "billing software",
"features": [
"Create subscription plans",
"Charge for usage",
"Manage recurring subscriptions"
],
"tags": [
"subscriptions",
"invoicing",
"usage_based"
],
"url": null,
"pricing": null
},
{
"name": "Terminal",
"type": "product",
"description": "A set of tools for businesses to accept in-person payments through Stripe, including card-present checkout that can be coordinated with online payments.",
"category": "point-of-sale payments",
"features": [
"Accept in-person card payments",
"Unify online and in-person payments"
],
"tags": [
"in_person",
"point_of_sale",
"payments"
],
"url": null,
"pricing": null
}
]
},
"brand": {
"voice": {
"summary": "Stripe speaks with an assured, intellectually ambitious business voice, addressing companies directly while grounding big economic ideas in practical outcomes. Its copy pairs concise product-led claims with precise metrics and technical explanations; the About page’s phrase “improving the conditions for economic growth and prosperity” captures its recurring focus on growth, infrastructure, and scale.",
"attributes": [
"measured",
"ambitious",
"technical",
"precise"
],
"avoid": [
"breathless hype",
"folksy banter"
]
},
"style": {
"summary": "Stripe’s lowercase “stripe” wordmark is a compact, bold sans-serif logotype, distinctive for its clean, unadorned letterforms rather than a separate emblem. The visual system pairs crisp geometric sans typography with a predominantly white canvas, deep navy and blue-gray text, vivid violet accents, and expressive gradients or abstract flowing color forms, balanced by spacious layouts and restrained product imagery.",
"attributes": [
"minimal",
"geometric",
"editorial",
"bold",
"polished"
]
}
},
"competition": {
"competitors": [
{
"name": "Adyen",
"domain": "adyen.com",
"type": "direct",
"category": "payment processing",
"positioning": "Enterprise-focused global payments platform with a unified commerce offering.",
"overlap": [
"Online card processing and local payment methods",
"In-person payments through point-of-sale terminals",
"Enterprise merchants and global payment operations"
]
},
{
"name": "PayPal",
"domain": "paypal.com",
"type": "direct",
"category": "payment processing",
"positioning": "Consumer-recognized wallet and merchant payments provider with broad online checkout adoption.",
"overlap": [
"Online payment acceptance for businesses",
"Digital wallet checkout",
"Small-business and enterprise merchant services"
]
},
{
"name": "Checkout.com",
"domain": "checkout.com",
"type": "direct",
"category": "payment processing",
"positioning": "Enterprise-oriented payment processor focused on digital businesses and global scale.",
"overlap": [
"Online payment processing",
"Global acquiring and local payment methods",
"Large digital merchants"
]
}
]
}
}{
"message": "Bad Request"
}{
"message": "Unauthorized"
}{
"message": "Payment required. Either authenticate with a Brandfetch API key (Authorization: Bearer <key>) or pay for this request with x402: sign the payment described in the PAYMENT-REQUIRED header and retry with a PAYMENT-SIGNATURE header.",
"documentation": "https://docs.brandfetch.com/agents/pay-per-request",
"pricing": {
"route": "GET /v2/brands/*",
"price": "$0.10"
},
"resource": "https://api.brandfetch.io/v2/brands/nike.com",
"standingAccess": "For many requests, POST /v2/agents/access (paid the same way) provisions an API key preloaded with prepaid credits."
}{
"message": "<Not Found> or <Invalid Domain Name>"
}{
"message": "We couldn't read this domain (the site appears to block automated requests)."
}{
"message": "API key quota exceeded"
}{
"message": "The brand context for this domain is still being generated. Retry in 30 seconds."
}Authorizations
Path Parameters
Domain name (brandfetch.com), a website URL on the domain (https://www.brandfetch.com/developers/pricing), or an email address on the domain (john@example.brandfetch.com). The API resolves a website URL or an email address to its registrable domain before the lookup. It does not store the URL or the address. Your request logs show only the domain. A URL whose host is not a domain name returns 400. A malformed address also returns 400. The API does not bill these requests.
Query Parameters
When true, return a brand context only if one is already cached, responding instantly without crawling the domain. If no cached context exists, the API responds with 204 No Content instead of resolving the domain live (which can take several seconds). Useful for latency-sensitive use cases. Any value other than true (including omitting the parameter) keeps the default behaviour of resolving the domain live on a cache miss. Defaults to false.
Response
Successful request. The response format is determined by the Accept header: application/json returns a structured JSON object, while text/markdown returns the brand context as Markdown. A request paid with MPP whose response was lost can be retried with the same credential for two minutes: it is served from the payment already taken and not charged again.
Full brand context returned by the Brand Context API. Note: unlike other endpoints in this API which use camelCase, the Brand Context endpoint intentionally returns field names in snake_case (e.g., canonical_name, resolved_at, value_proposition, target_audience, products_and_services) to align with conventions commonly used by LLM tooling that consumes this data.
Was this page helpful?