Brand truth.For AI & Agents.
Your brand. One canonical source. Owned by you, signed, and updated in one place. Connect compatible tools to your published brand context. They can read the current version.
We build the one source
your agents check first.
The Brand Context Protocol (BCP) turns everything your teams already know into one structured, agent-readable source. Every department, every tool, every freelancer, and every agency you work with reads the same brief instead of inventing their own.
Encoded Brands
Control, made simple.
Your voice, your claims, your boundaries, held in one source you own. Authored once, used everywhere. Always current. Always under your control.
Connect every agent & AI tool.
Every team and tool that touches your brand reads from one place you manage, not twelve people improvising.
Onboard employees & partners with a link.
Brand context gets re-typed into every prompt, every tool, every time. A canonical source is read once and reused.
No slop. Full stop.
Without your voice on record, AI fills the gap with the average of everyone else in your category.
About 15 minutes to set up.
Update it whenever you like.
Run the Encoder.
Upload your brand materials. Answer a few focused questions. Review your BCP.
Publish to the Registry.
Publish your signed BCP to Registry. Share one link with your tools and team.
Update it anytime.
Edit and republish anytime. Connected tools get the update on their next read.
Start in the AI your team already uses.
Copy one short starter into a new chat. It points your AI at our Encoder, uses the source material your chat can access, and asks a few pointed questions to fill in any gaps. You'll see a draft for confirmation before anything goes live.
Help me encode my brand into a public Brand Context Protocol. Start here: https://encoder.encodedbrands.ai/.well-known/agent-commerce.json. Use the owner-authorized quickstart/MCP handoff in that discovery document, not the Encoder GUI. Show me the proposed result for confirmation. Do not publish until the owner approves.
COMPATIBLE WITH CHATGPT · CLAUDE · GROK · COPILOT AS A CUSTOM MCP CONNECTOR
Get started today.
Your first full encode and signed Registry record are free. The record remains available while you keep it published, and you can withdraw it. Every Registry publication is integrity-signed, and DNS domain verification is free. Upgrade when you need to control access, know who used gated material, and prove what was live.
- One complete encoding
- All eight standard BCP files to keep
- Signed Registry record, available while published. Withdraw it when you choose.
- Free domain verification
- Free manual revisions
- Re-encode with the Encoder for $49
- Docs, community, and self-serve tools
- No human support. Included with Registry Certified.
- Certification mark on your Registry record
- Machine-readable certification status for AI agents
- Named audit for authenticated gated access
- Control who can receive gated context
- Unlimited teammates, no per-seat charges
- Up to 100 AI-assisted re-encodes per year included
- Version history and publication audit trail
- Signed history, diffs, and restore
- Priority human support
- Everything in Registry Certified
- Custom plugins for all your tools
- Multi-brand and multi-market support
- Guided stakeholder interviews
- Brand audit and source review
- Claims, boundaries, and representation rules resolved with the team
- Done-with-you encoding
- Registry rollout and AI-agent testing
- Priority implementation support
Registry reads, integrity signing, and optional DNS verification are free. Registry Certified adds named audit and access control for authenticated gated material, certification status, team access, and support. Read the docs →
Frequently asked questions.
What is the Brand Context Protocol?
Brand Context Protocol creates a standing brief that AI tools and agents you connect can read before they write, place, or represent your brand. The result can be more consistent, more faithful output without re-briefing each connected tool every time.
Why do I need it? What problem does it solve?
AI tools do not reliably start with your current brand context. Many teams paste guidelines into system prompts one tool at a time, which consumes session context and can drift. BCP gives the agents you connect access to the same brief, from the same source, updated in one place.
What about my existing brand guidelines?
Your brand guidelines matter, but PDFs are not a reliable machine-readable source across AI tools. Encoded translates your guidelines into a structured form that tools you explicitly connect can read, subject to each tool's URL or MCP support and controls.
What is the process to get it live?
Encode, publish, then update. Start in the AI your team already uses with Quickstart or MCP, or use the guided Encoder. Either path encodes the brand you already have. You review, then publish. Your BCP is hosted in Registry by default after you publish. Update anytime. Connected agents pick up the current version the next time they read it. Start with Quickstart: copy the starter on this page, or point your agent at https://encoder.encodedbrands.ai/.well-known/agent-commerce.json. Prefer the guided Encoder? Open https://encoder.encodedbrands.ai/encode. Connect compatible tools with the MCP guide and docs. Those are custom remote connectors you configure, not a native endorsement by the tool vendors. Your web team can also serve /.well-known/brand.md on your own domain as a short pointer to that Registry record.
Is our brand information secure?
Your brand voice, claims, and boundaries are designed to be read by agents. That's the point. You control what goes in. Nothing is published without your review. The Registry hosts your BCP files until you take them down. Gated access to confidential messaging matrixes is coming soon.
How long does it take?
The Encoder session takes 30 minutes to an hour. Enterprise engagements are scoped to your organisation, typically one to two weeks from kickoff to published BCP.
What do I need to prepare?
Whatever you have. Existing brand guidelines, tone-of-voice docs, positioning decks, campaign examples. The Encoder works with what exists. If you have nothing, the interview builds your BCP from scratch.
Where does it live?
By default, your published BCP is hosted at a Registry URL. Serving it at /.well-known/brand.md on your own domain requires setup by you or your web team. The recommended domain file is a short pointer to the Registry record, not a copy of the full package. Once configured, tools with URL access can fetch it there. Agents that search Registry can also discover your published record without already knowing your domain.
Will this work with our existing tools and agencies?
Your team, your agencies, and the AI tools you already use can work from the same brief, once you connect them. Public Registry reads are free over a URL or Model Context Protocol (MCP). You can add Encoded's public Registry MCP as a custom remote connector in ChatGPT, Claude, and Grok, subject to each product's plan, client, and administrator controls. Agencies and providers can use the same source where their tools permit URL or MCP access. Need gated private context? Registry Certified adds access control, team governance, version history, and audit evidence for who pulled protected context, when, under which grant, and against which section and content hashes. You configure those connections. It does not mean those vendors natively adopt, automatically read, or endorse BCP or Encoded Brands. Setup notes live in the MCP guide.
How do we know this works?
We publish our own brand context. The file at encodedbrands.ai/.well-known/brand.md is a discovery pointer. Check the Registry's separately signed canonical package, its version, and its provenance before relying on it. If we wouldn't use it for our own brand, it doesn't ship.
We encode our own brand first.
Our brand is live, in public.
A company that makes AI sound like your brand had better sound like itself. Our domain file at encodedbrands.ai/.well-known/brand.md is a discovery pointer. The Registry separately shows the signed canonical package, including its published version and provenance.
Whatever voice, structure, and decisions we bake in carry across every brand that builds on the standard. We set the example in public.
If we wouldn't use it for our own brand, it doesn't ship.
Loading the current signed Registry voice.md…
Talk to Encoded.
Questions about encoding your brand, Registry Certified, or Enterprise? Send us a note. We will reply by email.