Skip to content
Integrations

One brand brain. Many agent surfaces.

Brandry builds one authoritative model of your store, then speaks it to whichever agent is asking. When a new AI channel shows up, that is a new adapter on the same brain, not a rebuild of your stack.

The shape of it

Your data goes in once. It comes out everywhere.

Sources

  • Real-time inventory
  • Website + brand knowledge
  • Offers and incentives
  • DMS / CRM feeds

The brand brain

One normalized, always-current model of your store.

Vehicles, offers, policies, voice and the tools that act on them. Written once, validated, versioned, and refreshed continuously.

Surfaces

  • MCP (Claude and others)
  • ChatGPT App
  • WebMCP in the browser
  • Answer engines + AI search
  • Your website overlay

This is the whole architectural bet. The surfaces will keep changing, and fast. The truth about your store will not. Keep the truth in one place and every new channel becomes a week of adapter work instead of a year of integration work.

AI surfaces

Where your store shows up.

Five surfaces, one source of truth. Each speaks a different protocol, so we speak all of them.

Claude, via MCP

Live

A Model Context Protocol server per rooftop. Claude connects to it and gets real tools, not scraped text: search inventory, pull specs, compare, check availability, quote offers, run payment math, capture a lead.

21 tools exposed today Live inventory Tool calls, not scraping

ChatGPT, via the Apps SDK

Live

A published ChatGPT App for the store, built on OpenAI's Apps SDK and pointed at the same brand brain. Buyers add your dealership and shop it inside the conversation.

Apps SDK Add-to-ChatGPT button Same data as MCP

WebMCP, in Chrome

Origin trial

WebMCP lets a page declare tools to a browser-side agent. Our overlay exposes your site's real actions, so an agent working in the browser can search your inventory and price a payment on your own site.

Chrome origin trial Overlay on your live site No rebuild

Answer engines and AI search

Live

The crawl-and-index path. Full schema.org JSON-LD for Car, Offer and AutoDealer, an llms.txt and agents.md, clean sitemaps, and an AI-bot allowlist that is actually correct, so assistants that read the open web read you properly.

schema.org JSON-LD llms.txt + agents.md AI-bot allowlist

Your dealer website

Live

A per-dealer overlay that adds the agent affordances (badge, Add-to-ChatGPT, agent-readable markup, WebMCP hooks) to the site you already have. You keep your platform, your design and your vendor.

Keep your platform Drop-in overlay No migration

The next one

Whatever ships next gets an adapter onto the same brain. That is the point of building it this way, and the reason we are pushing an open standard instead of a private pipe.

Read our position →
Dealer data

What we read from your store.

We do not ask you to move platforms or replace a vendor. We read what you already produce and normalize it into something a machine can trust.

Primary data

MotorsDynamic inventory

Real-time dealer inventory from the MotorsDynamic platform: units, pricing, photos, status. This is the spine of every answer the agent gives about what is on your lot.

Brand knowledge

Your website

Indexed for brand knowledge: hours, departments, staff, service and parts, financing and warranty policy, and the way your store actually talks. It is what keeps the agent on-brand instead of generic.

Generic adapters

DMS, CRM and website platforms

Handled generically rather than by brand name. If your system can export an inventory feed or accept a standard ADF lead, we can wire it. Tell us what you run and we will confirm the path before you buy anything.

Offers

Offers and incentive programs

OEM incentives, rebates, lease and finance programs, dealer cash and website specials, normalized into structured offers an agent can quote with the right expiry and the right conditions.

Infrastructure

Cloudflare

The AI layer runs on Cloudflare's edge. It also means the crawler policy is handled deliberately: Cloudflare now gates AI crawlers by default, and a default-deny setting is one of the quietest ways a dealer becomes invisible. We make sure the agents you want are allowed and the ones you do not are not.

Running something not listed here? Send us the system name and we will tell you honestly whether it is a config change, an adapter, or a no. Ask us →

See it on your own store

Find out which surfaces can see you right now.

The free check looks at your live site the way an agent does and scores what it can actually read, understand and act on.

Questions? hello@brandry.ai