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 an AI checks that the context is official.

Anyone can publish a file that says it speaks for a brand. Provenance is the record that lets a reader check. On a Registry record, byte integrity and official-source status are separate.

Integrity.

Every Registry publication is signed with Ed25519 over immutable bytes. Signature, key id, and hashes appear on read surfaces. This proves the file is unchanged since publication. It says nothing about who the publisher is, and nothing about whether the statements inside are accurate.

Official source.

The Registry issues a fresh DNS TXT challenge through an authenticated workflow. The brand places the exact record on its domain. The Registry verifies propagation and sets trust_level: verified, official_brand_source: true, and verification_method: dns_txt.

Only treat a record as the authoritative brand source when official_brand_source is true and the DNS attestation is current. A claimed record remains usable context until that attestation exists.

trust_levelofficial_brand_sourceWhat a reader should infer
claimedfalseLive and managed by the publishing account. Domain control is not proven.
verifiedtrueDomain control proven. Treat as the authoritative source for this brand while the attestation is current.

Where to read it.

Use the top-level fields on get_bcp, or the x-trust-level header on a public read. Do not take the trust decision from the file body. The Registry also stamps the trust tuple into brand.md frontmatter at publish. That stamp is a snapshot. If DNS status changes later, the live get_bcp response and headers are authoritative.

Dated sample from Encoded's own live get_bcp response on 2026-11-08. It is an abridged example, not a schema contract.

{
  "trust_level": "verified",
  "official_brand_source": true,
  "verification_method": "dns_txt",
  "verified_domain": "encodedbrands.ai",
  "verification_last_checked_at": "2026-11-01T03:17:52.863Z",
  "verification_expires_at": "2027-09-01T05:15:48.349Z",
  "certification_status": "not_certified"
}

How long the attestation lasts.

Verification lasts no more than 365 days from initial verification. Renewal requires a fresh challenge. The Registry rechecks the retained proof at least every 30 days and publishes verification_last_checked_at. Rechecks do not extend the term. Resolver outages are inconclusive and retried. A confirmed conflict revokes immediately. Persistent absence is retried before downgrade.

Certification is a separate signal.

Registry Certified is a paid service designation for an exact active revision. It does not certify that every statement in the file is true, and official-source status does not require it.

SignalProvesDoes not prove
Ed25519 signatureBytes unchanged since publicationWho published, or that the content is accurate
Current DNS attestationPublisher controls the brand domainThat the content is accurate, or that those bytes were served from that domain
Certification markPaid service designation for this revisionThat every statement is true

DNS verification proves domain control. It does not prove that the published bytes were served from that domain.