Skip to main content
If you write your integration with an AI coding tool, this page gives it what it needs to get the integration right the first time: the docs as context, the API as a tool, and a prompt to start from. There are two different things you can connect, and they are easy to confuse: Connect the docs server when you are building with Brandfetch. Connect the Brandfetch server when your assistant needs brand data itself, such as making a deck in a client’s colors.

Give your AI the docs

If your tool does not support MCP, give it a file instead:

Start from a prompt

Paste this into your coding assistant and edit the first line to describe what you are building.
Prompt
Every use case page also ends with a prompt tailored to that build.

Give your AI brand data

To let Claude, Cursor, Codex, or your own agent look up brands while it works, connect the Brandfetch MCP server. It signs you in with OAuth and exposes tools for brand search, brand data, brand context, transaction enrichment, and logo URLs.
Claude Code
The MCP setup guide covers Claude, Codex, Cursor, VS Code, and other clients.

Agents without a human

An autonomous agent can discover Brandfetch, get access, and pay without anyone signing up:
  • brandfetch.com/agent-onboarding/SKILL.md is an agent skill that walks through choosing an API, getting a credential, and making the call.
  • Pay per request lets an agent pay $0.10 per Brand API, Brand Context API, or Transaction API call with x402 or MPP.
  • Discovery lists every machine-readable document Brandfetch publishes, including the API catalog and MCP server card.