Make every dealership legible to AI. Then make it open.
Shopping moved to AI assistants faster than the industry's websites did. Brandry exists to close that gap for the dealer, and to push an open standard so closing it does not mean handing the keys to a single vendor.
The shopping journey moved. The websites did not.
A buyer used to open five dealer sites and a marketplace. Increasingly they open one chat window and ask a question in plain language: which three-row SUV fits six hundred a month, does anyone near me have one, can I get it this weekend. The assistant answers. The buyer goes where it says.
That answer has to come from somewhere. If your inventory is rendered by JavaScript, your specs live inside an image, your offers are a PDF and your crawler policy quietly blocks AI bots by default, then it does not come from you. The assistant does what it always does with missing data: it works with what it can read, and recommends someone else. You are not being outranked. You are being skipped, and nothing in your analytics tells you it happened.
What we actually build
Brandry is a layer that sits over the store you already have. You keep your website, your CRM, your vendors and your process. We make three things true that were not true before: machines can read your store correctly, assistants can answer questions about it from live data, and the agent has real tools to do the work, estimate a trade, run a payment, match a budget to a unit, hand a lead to your CRM.
We measure it out loud. The public checker at isitagentready.com scores any dealership URL on what an agent can actually see and do. Dealers typically land around 21 out of 100 before they change anything. With the Brandry layer in place the same store scores 100 out of 100, Level 5, Agent-Native. That is not a projection, it is a number anyone can reproduce against a live site.
The part that is bigger than us
Here is the uncomfortable version of the opportunity. Right now, connecting one AI assistant to one dealership system is a bespoke project: weeks of work, tens of thousands of dollars, brittle the moment either side ships a change, and completely non-reusable. Multiply that by every assistant and every DMS, CRM, desking tool, scheduler and parts catalog in the country and you get an N times M problem that no amount of funding brutes its way through.
The fix is a shared protocol, which is why we are helping drive AutomotiveMCP, a proposed open standard (draft RFC v0.1) for how dealership systems expose inventory, CRM, desking, service and parts to agents over the Model Context Protocol. It has a specification, versioned JSON Schemas, an adoption directory, a certification mark and deliberately neutral governance. Brandry is a reference implementation and a founding participant, not the owner.
We are aware of how that sounds coming from a vendor. So, plainly: a ratified open standard is worse for our moat and better for the industry, and we think it is the correct trade. A walled garden would let one company sit between every dealer and every AI, and rent that position forever. Dealers have been on the wrong side of that arrangement enough times already.
Four positions we will not trade away.
The dealer should own the answer
When a buyer asks an assistant which dealer to go to, the answer should come from the dealer's real inventory, real offers and real policies. Not from a third-party aggregator's summary of them, and not from a model's best guess.
Readable beats loud
For thirty years the digital playbook was to be louder: more spend, more pages, more leads. An agent does not respond to loud. It responds to structured, current, verifiable. That is a genuinely different game and most of the industry has not noticed it started.
Proof over positioning
Anyone can say they are AI-ready. We built a public checker so it is a number, not an adjective. If our own claim cannot survive a URL and sixty seconds, it is not a claim worth making.
Open beats owned
The pipe between AI agents and dealership systems should be a standard, not a product. We would rather build the best implementation of an open protocol than the only implementation of a private one.
Helping define the open standard for AI in automotive retail.
Every AI-to-dealer integration built today is bespoke wiring between one assistant and one system. AutomotiveMCP is a proposed open standard (draft RFC v0.1) for how dealership systems expose inventory, CRM, desking, service and parts to AI agents over the Model Context Protocol, so any agent can speak to any system the same way. Brandry is a reference implementation and a founding participant.
What the draft covers
- Specification. How dealership systems expose data and tools to agents
- JSON Schemas. Versioned shapes for inventory, CRM, desking, service, parts
- Adoption directory. Who has implemented what, in public
- Certification. A conformance mark, so claims can be checked
- Governance. Neutral, so no single vendor owns the pipe
See what an agent sees when it looks at your store.
Free, in about sixty seconds, no sales call required to find out where you stand. Then decide how far up the ladder you want to go.
Questions? hello@brandry.ai