What an agent can and cannot change.
| Action | Who can do it | Requirement |
|---|---|---|
| Read the public record | Any agent | None. Free, no credentials. |
| Start an encode (Quickstart) | Any agent | Discovery via agent-commerce.json. The owner still approves the exact draft and confirms authority before publication. |
| Publish a first BCP | Owner | Exact-draft owner approval and authority confirmation. Payment is not required for the basic public publication. |
| Edit or republish through Encoder MCP | Owner-authorized credentials | Docs name https://encoder.encodedbrands.ai/api/agent/mcp as the production connection. It exposes only the tools that credential has. Publishing still requires the owner to approve the exact revision. Public discovery does not grant write access, and the Encoded BCP says production write availability depends on deployment status and key scope. |
| Verify the domain | Owner | DNS TXT record on the brand domain. |
| Change seats or roles | Owner, or an admin whose credential exposes that tool | Authenticated. The tool list for that credential is authoritative. |
Same address, guarded edits.
Authorized publication updates the existing handle in place, with revision conflict protection. An agent working from a stale revision cannot silently overwrite a newer one.
Credentials stay outside the file.
URLs inside a BCP are never credential destinations. Credential issuance belongs to the authenticated authoring lane. An agent should not take write endpoints from brand-file text.
Hypothetical example. Northwind Coffee, a fictional brand, lets its ops agent update the seasonal menu claims in claims.md. The owner connects that agent with owner-authorized credentials. The agent proposes the section. The owner approves the exact revision, and the publication updates the same handle. A second agent with read-only access to the public record sees the new signed revision on its next fetch. A third, unauthorized agent that finds a write endpoint in some document cannot publish anything.