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.

How a change becomes the approved version.

  1. Propose. An editor edits the files directly or requests an AI-assisted revision. Manual revision is free. A full AI-assisted re-encode is priced per use. See pricing.
  2. Review. The owner reads the exact draft that would publish.
  3. Approve and publish. Authorized publication updates the existing handle, with revision conflict protection so two editors cannot overwrite each other unknowingly.
  4. Sign. The Registry signs the new publication bytes with Ed25519.
  5. Record. On Registry Certified, an owner connection with the required scope can inspect signed publication history, diffs, and restore options for retained publications. Restore still requires publication approval. A revision that was never retained cannot be restored.

Living document.

A BCP is updated as often as the brand changes. It does not update itself. Drift detection, which compares output against a published BCP, is in development and limited to narrow comparisons today.