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.

Proving what was live.

When an agent produces something off-brand, the first question is whether the agent was given the right rules. A governed BCP makes that answerable for the bytes Encoded served.

  • Signed bytes. Each Registry publication is signed. Hash and signature identify exactly what was served.
  • Revision ids. Each publication has a revision id, visible on read surfaces.
  • History. Registry Certified includes signed history, diffs, and restore for retained publications, plus a machine-readable certification status for the active revision. The mark records a paid service designation for that revision. It does not certify that every statement is true. Restore still requires publication approval. A revision that was never retained cannot be restored.
  • Gated access record. For authenticated gated material, the named audit ties a principal to the revision and content hash it received.

What this cannot show: what the agent did with the context after receiving it. That record lives in the agent's own logs.