Your teams already know the brand. We turn that knowledge into one signed source, aligned across your organization, published for your agents, and kept current for as long as you use it.
The Encoder works like a world-class brand strategist. It studies what already exists across your site and documents, positions you against your category, then interviews you to draw out what only you know. One session becomes a structured BCP draft for your review; Registry publication signs the approved files.
These diagrams show an illustrative BCP v1.1.0 package, not Encoded's signed files. Check our live Registry root for the version currently served.
Publish approved files to Registry or serve the package on your own domain. Connect compatible tools with a read URL or MCP connector. A domain pointer can help agents discover a Registry record, but a known handle can be read directly. Connected tools can fetch the current publication when they request it; publishing alone does not configure them.
Scroll to see connected tools
Registry publication keeps a signed, versioned package at a stable handle. You can add a domain discovery pointer and separately verify domain control with a time-limited DNS attestation; neither happens just by publishing. Revise and republish as your brand changes. A connected tool can read the new revision when it next fetches the source.
The free Encoder takes one owner through a complete encoding. Registry Certified adds team access and priority human support. When multiple brands, stakeholders, or markets make coordination the hard part, Enterprise adds guided discovery, claims and boundaries resolved together, and voice reconciled across the room. One source, aligned across your organization.
The Brand Context Protocol is an open standard. It takes what your brand already says in public and organizes it into one structured source you own. Serve the package on your domain or publish it to a Registry handle; the files stay portable.
The canonical root: brand identity, summary, and URLs for public daughter files. A domain discovery pointer, when used, is separate.
Voice modulated by audience. How the brand sounds to a prospect versus a customer versus a regulator.
What the brand can and cannot claim. Each claim paired with verifiable evidence.
Anti-patterns. The things the brand never says, never does, and never sounds like.
Operational values: specific behaviors any agent can apply to a content decision.
How the brand wants to be described in AI-generated answers and third-party contexts.
Logo, color, typography, and imagery rules — the visual identity in a form agents can reference.
Language patterns to avoid — words, phrases, and constructions the brand never uses, especially those that read as AI-generated.
Where your client, plan, and administrator allow a custom remote MCP connection, use our setup guide to add the public Registry endpoint.
Connect the BCP as brand context data. Your tool's own policy stays in charge.
Connect through an MCP-capable client or use the setup notes we provide. Registry Certified includes priority human support; Enterprise includes implementation support.
Connect through an MCP-capable client or your own integration. Registry Certified includes priority human support; Enterprise includes implementation support.
Connect through a Registry URL, MCP-capable client, or your own integration. Registry Certified includes priority human support; Enterprise includes implementation support.
Developer docs, reference implementation, and MCP endpoint spec included.