Choose your path

Choose where to start.

Create a Brand Context Protocol from your existing material, or return to a brand you already manage. You review the result before anything is published.

Add Encoded Brands from the connector directory

Add Encoded Brands from the connector directory. If it is not listed, add https://encoder.encodedbrands.ai/api/agent/mcp as a custom connector.

On Team or Enterprise plans, an owner may need to allow it.

In ChatGPT, open its app or connector settings. Look for an option to create an MCP app or add a custom connector. Your plan or workspace admin may hide it.

If that option is missing, choose the guided Encoder. You can connect your tools later.

An Encoded Brands site.

Your brand context leaves with you.

Brand libraries inside a single design tool or model vendor work well inside that product. Your assistants are spread across several products. A BCP is plain markdown at a well-known path, so any tool that can fetch a URL can read it.

Three ways to run it.

Self-hostedRegistryBoth
Where files liveYour domain at /.well-known/registry.encodedbrands.ai/{handle}/Same bytes in both places
Signed publicationYour choiceEvery publication Ed25519-signedRegistry copy signed
MCP deliveryYou build itIncludedIncluded
Domain verificationYour domain is the sourceFree optional DNS verificationDomain plus Registry attestation
CostHosting you already havePublic record free. See pricing.

Encoded publishes its own BCP both ways: at encodedbrands.ai/.well-known/brand.md and on the Registry.

Leaving.

Download the package at any time. The files keep working wherever you host them. The paid Registry layer has to earn renewal through trust and operations, not lock-in.