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.

When the agent starts the encode.

An agent can begin an encode on a brand's behalf. It cannot make the result official on its own.

Quickstart, free.

Discover it at agent-commerce.json. The offer key is byo_ai_onboarding. The tool is begin_onboarding. It publishes a basic signed public BCP after the owner approves the exact draft and confirms authority. Payment is not required for that basic publication. The same document is the contract for the prepaid registration path. Confirm it before acting.

Agent registration, prepaid.

First encode, API key issuance, and a machine-payment rail. Price and contract are on the live discovery document, not in this page.

What stays with the owner.

Exact-draft approval, including authority confirmation, happens before publication. An edit or publish through the production Encoder MCP requires owner-authorized credentials for that account. The connection only exposes the tools that credential has, and publishing still requires the owner to approve the exact revision. Domain verification needs the owner's DNS. Public discovery alone never implies write access. The authenticated tool list is authoritative. Production availability also depends on key scope, as the Encoded BCP states.