Brandfetch integration: operations for AI agents
Brandfetch connects to Type.com as an integration. This page lists the 14 operations documented for Claude and Codex in Type.com: 10 read, 3 write, 1 destructive.
About Brandfetch
Brandfetch offers an API that retrieves company logos, brand colors, and other visual assets, helping marketers and developers maintain consistent branding across apps
Categories: Design & Media
How to connect Brandfetch to Type.com
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
14 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
brands
- Read
Get brand data
Get brand data using a Domain, Website URL, Email address, Brand ID, ISIN, Stock/ETF ticker, or Crypto symbol. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
GET /v2/brands/{identifier} - Read
Get brand data by domain
Get brand data using a domain name. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
GET /v2/brands/domain/{domain} - Read
Get brand data by Stock or ETF ticker
Get brand data using a Stock or ETF ticker. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
GET /v2/brands/ticker/{ticker} - Read
Get brand data by ISIN
Get brand data using an ISIN code. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
GET /v2/brands/isin/{isin} - Read
Get brand data by crypto symbol
Get brand data using a crypto symbol. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
GET /v2/brands/crypto/{symbol} - Read
Get brand data from a transaction
Turn payment transactions into merchant data. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
POST /v2/brands/transaction - Write
Check availability and prefetch a brand
Tells you whether Brandfetch already holds the brand and, when it does not, queues a crawl so that the `GET` which follows is answered from our store instead of waiting on a live crawl. Available on paid plans. A `HEAD` request carries no body and never consumes a credit. - `200` — the brand is held. A `GET` answers from the store. - `202` — the brand is not held and a crawl has been queued. A `GET` made before the crawl finishes still crawls live. - `404` — nothing can be fetched for the identifier: an unknown brand ID, ticker, ISIN or crypto symbol, a domain without a public suffix, or a brand that has been removed. Prefetch requests may be throttled to prevent abuse and ensure quality of service. A typical use is warming a brand at signup: send the new user's email address, and the brand is ready by the time you render it.
HEAD /v2/brands/{identifier} - Write
Check availability and prefetch a brand
Tells you whether Brandfetch already holds the brand for a domain and, when it does not, queues a crawl so that the `GET` which follows is answered from our store instead of waiting on a live crawl. Available on paid plans. A `HEAD` request carries no body and never consumes a credit. - `200` — the brand is held. A `GET` answers from the store. - `202` — the brand is not held and a crawl has been queued. A `GET` made before the crawl finishes still crawls live. - `404` — nothing can be fetched: the domain has no public suffix, or its brand has been removed. This route accepts a domain only; like the other explicit type routes it refuses an email address with a `400`. Prefetch requests may be throttled to prevent abuse and ensure quality of service.
HEAD /v2/brands/domain/{domain} - Write
Get up to 100 brands in one request
Send up to 100 identifiers. Get one result per identifier, in the order you sent them. Each identifier is answered the way `GET /v2/brands/{identifier}` answers it. One difference: a batch never crawls while you wait. A brand that is not indexed yet is queued for indexing and answered `202`. Request it again later. Each identifier answered `200` uses one API credit. Every other result is free, `404` included. An identifier repeated in one request is charged once. Available on paid plans and with prepaid credits. Authenticate with an API key sent as `Authorization: Bearer <key>`.
POST /v2/brands/batch
Search
- Read
Search brands
Search for brands by name, login to get a clientId
GET /v2/search/{name}?c={clientId}
context
- Read
Get brand context by domain
Get a structured, narrative-rich brand context for a domain — including identity, positioning, products and services, voice, visual style, and competitors. Authenticate with an API key sent as `Authorization: Bearer <key>`, or pay for the single request with x402 or MPP: https://docs.brandfetch.com/agents/pay-per-request.
GET /v2/context/{domain}
viewer
- Read
Get the authenticated viewer
Returns the identity of the credential used to authenticate the request: an API key or a user session token (JWT). Use it to verify a credential during integration setup (a `200` response means the credential is valid; `401`/`403` means it is missing, unknown, or revoked) and to display which API key and organization are connected. A key an [agent bought](/agents/overview) also says how it was paid for and how to add credits. Requests to this endpoint are free: they never consume API credits.
GET /v2/viewer
agents
- Read
Describe the agent access offer
What an agent can buy and how to pay for it: standing API access — an organization, an API key preloaded with prepaid credits and an MCP token — sold for one x402 or MPP payment. Needs no credential. Written for an agent that will act on it. See https://docs.brandfetch.com/agents/overview.
GET /v2/agents/access - Destructive
Buy standing access with an x402 or MPP payment
Pay a whole number of US dollars to receive a Brandfetch organization, an API key holding 20 prepaid API credits per dollar, and an MCP bearer token. One credit is one Brand API, Brand Context API or Transaction API request. Call once without a payment to receive the 402: its `PAYMENT-REQUIRED` header is the x402 challenge (USDC on Base), its `WWW-Authenticate` header the MPP challenges (USDC.e on Tempo, or a card through a Stripe shared payment token). Pay one and repeat the request with the result — `PAYMENT-SIGNATURE` for x402, `Authorization: Payment …` for MPP. A wallet owns the organization it buys: paying again from the same wallet adds credits to the same key, and `rotateKey=true` replaces the key while doing so. A card names no wallet, so each card payment buys its own organization and key. The API key and MCP token are returned once, in the response that completes the purchase, and a payment is never charged twice. A later request carrying the same payment is answered `409` without them: a settled payment is public (an x402 signature is on-chain), so presenting it proves nothing about who sent it. If the purchase is answered with a `500` that says to retry, or with no response at all, retry the exact request at once: the first retry to succeed within three minutes of the payment receives the credential, unless it was already returned in a response the client lost, which is answered `409` `credential_already_delivered`. The credits are granted whether or not the credential is returned. See https://docs.brandfetch.com/agents/overview.
POST /v2/agents/access
No operations match.
See How connections work for access and permissions, or browse all integrations.