{
  "trust_level": "verified",
  "official_brand_source": true,
  "verification_method": "dns_txt",
  "verified_domain": "brandcontextprotocol.dev",
  "verified_at": "2026-09-04T04:57:42.597Z",
  "verification_last_checked_at": "2026-10-05T03:17:08.928Z",
  "verification_expires_at": "2027-09-04T04:57:42.597Z",
  "status": "active",
  "customer_handle": "brand-context-protocol",
  "certification_status": "not_certified",
  "registry_certified": false,
  "certification": null,
  "brand_name": "Brand Context Protocol",
  "response_scope": "full_tree",
  "integrity": {
    "version": 2,
    "publication_id": "7e384b84f164d08199212cbd088b1365625aaaf6e468b6d552ae1d86a2212482",
    "revision_id": "54c62795-171c-4e01-bd2b-d51dac5ed067",
    "manifest_sha256": "24031b4ae1e445a4bfa4b1e6be58fd4846884ce35bd2e42e9e7762fc970e1c23",
    "manifest_signature": "vHwegvnqv832WgkPj5QAVecwdg1xV9+ZYBBpo1igegB0OLOnVuII8a/OMMjxACbGPVrIEGozuTduwxRt6OoyBA==",
    "manifest_signature_kid": "v1"
  },
  "verified": {
    "domain": "brandcontextprotocol.dev",
    "verified_at": "2026-09-04T04:57:42.597Z",
    "verification_last_checked_at": "2026-10-05T03:17:08.928Z",
    "verification_expires_at": "2027-09-04T04:57:42.597Z"
  },
  "schema": "bcp-readable-package-v1",
  "integrity_scope": "publication_manifest",
  "representation": "Derived readable representation; verify signatures against the canonical source files.",
  "canonical_registry_url": "https://registry.brandcontextprotocol.dev/brands/brand-context-protocol",
  "html_url": "https://registry.encodedbrands.ai/brands/brand-context-protocol",
  "files": [
    {
      "path": "/.well-known/brand.md",
      "content": "---\nbcp_version: \"0.8\"\nfile_type: root\nbrand_name: \"Brand Context Protocol\"\ntree_version: \"1.3.1\"\nwebsite: \"https://brandcontextprotocol.dev\"\ntagline: \"Machine-readable brand context at a well-known location.\"\nlast_updated: 2026-09-02\ndefault_locale: \"en-US\"\npublication_profile: registry_backed\ncanonical_bcp: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand.md\nregistry_mcp: https://registry.brandcontextprotocol.dev/mcp?customer_handle=brand-context-protocol\nregistry_handle: brand-context-protocol\nagent_first_action: \"fetch https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand.md\"\ndaughter_files:\n  voice: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/voice.md\n  voice_anti_ai: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/voice/anti-ai.md\n  values: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/values.md\n  boundaries: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/boundaries.md\n  claims: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/claims.md\n  representation: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/representation.md\n  visual: https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand/visual.md\n---\n\n# Brand Context Protocol\n\nThe Brand Context Protocol (BCP) is an open specification for publishing machine-readable brand identity at a well-known location on a brand's domain. AI agents generate content about brands every day. Without a source of truth they guess. BCP gives them the answer: a root brand.md at /.well-known/brand.md plus daughter files for voice, values, boundaries, claims, representation, and visual context.\n\nThe brand described in this file is the protocol itself, the open standard. It is not a company and not a product. The specification text is licensed CC BY 4.0. The schema and reference code are MIT. The source lives at https://github.com/Brand-Context-Protocol/spec. Encoded Brands authored the specification and maintains it with the community under a BDFL governance model with an RFC process. Encoded Brands also operates the reference Encoder and the public Registry as a separate commercial layer.\n\n## Core identity\n\n```yaml\ncategory: \"open specification for machine-readable brand context\"\ncurrent_version: \"0.8\"\nlicenses:\n  spec_text: \"CC BY 4.0\"\n  schema_and_code: \"MIT\"\nsource: \"https://github.com/Brand-Context-Protocol/spec\"\ngovernance: \"BDFL with a public RFC process\"\n```\n\n## For agents\n\nRead this file before you write about, implement, or build on the Brand Context Protocol. The agentic path through the ecosystem has five stages:\n\n### 1. Discovery\n\nA brand's discovery document lives at `https://{domain}/.well-known/brand.md`. It is either a complete self-hosted root or a rich Registry-backed root, like this site's own copy, that gives agents useful first-read context and points to the canonical Registry package. Registry-backed roots are served at `https://registry.brandcontextprotocol.dev/{handle}/.well-known/brand.md` and over MCP: `POST https://registry.brandcontextprotocol.dev/mcp?customer_handle={handle}`, tool `get_bcp`.\n\n### 2. Transaction\n\nThe protocol requires no vendor. Any producer can author a BCP by hand from the spec and serve it from a static host. The reference implementation, operated by Encoded Brands, also lets an agent purchase and run an encoding itself:\n\n- Commerce discovery: `GET https://encoder.encodedbrands.ai/.well-known/agent-commerce.json`. This live document is authoritative for the offer, transaction amount, payment challenge, credentials, and MCP path.\n- Registration: `POST https://encoder.encodedbrands.ai/api/agent/register`. The first request returns an HTTP 402 challenge. Retry the same body with a Stripe Shared Payment Token in `Authorization: Payment <credential>`.\n- The current machine offer is USD 499 one time for one API key and one complete encoding session. Subsequent AI-assisted encodings are USD 49 each.\n- MCP server: `POST https://encoder.encodedbrands.ai/api/agent/mcp`. Use the returned API key as `Authorization: Bearer <api_key>`, then call `initialize` and `tools/list`; the live tool list is authoritative.\n\n### 3. Completion\n\nAn encoding produces the seven canonical core files: brand.md plus voice, values, boundaries, claims, representation, and visual.\n\n### 4. Publish\n\nRegistry publishes are signed with Ed25519 over immutable canonical bytes and served at the handle the publish call returns. The brand-domain discovery pointer and the Registry publication are different artifacts. Self-hosting a complete tree at your own /.well-known/ path conforms equally. Ring 1, domain-first file discovery, is the only distribution layer the spec requires.\n\n### 5. Implementation\n\nBefore writing, designing, or answering for any brand, fetch its `/.well-known/brand.md` or call `get_bcp` on the Registry MCP. Load only the daughter files your task needs: voice for copy, boundaries and claims for safety, visual for creative, representation for describing the brand.\n\n## Change log\n\n- 2026-09-02: v1.3.1 -- Recorded the published protocol favicon and added automated checks that the domain and Registry packages stay byte-identical, signed, and verified.\n- 2026-09-01: v1.3.0 -- Connected the protocol's domain entry point to its dedicated Registry package, updated the agent transaction contract, and corrected current-version claims.\n- 2026-08-05: v1.2.0 -- Updated the protocol's self-hosted reference BCP to v0.8 and documented the domain discovery and canonical Registry publication split.\n- 2026-08-05: v1.1.0 -- Bumped every file in this tree from BCP v0.4 to v0.7 (frontmatter had drifted behind SPEC.md for two major revisions). Added voice/anti-ai.md as a registered daughter. Fixed a stale `current_version: \"0.4\"` claim in the body text that disagreed with the frontmatter.\n- 2026-06-11: v1.0.0 -- initial BCP for the protocol itself, authored from SPEC.md v0.4, GOVERNANCE.md, and the published site.\n",
      "signature": "Unwo2Rdl6SqJ6aAHo5ugJhun4CZISF+S98FsWASLyIYlaOVuLfF3n49KH4pFkDAkznjewVqwG+GiXv+oYpOOAA==",
      "sha256": "57721aed6576aa6dadbd04322bdb93d25951f88711b18da971236f64a0f1ba17",
      "kid": "v1",
      "content_type": "text/markdown; charset=utf-8",
      "html_url": "https://registry.encodedbrands.ai/brands/brand-context-protocol/files/brand",
      "json_url": "https://registry.encodedbrands.ai/brands/brand-context-protocol/files/brand/data.json",
      "source_url": "https://registry.encodedbrands.ai/brands/brand-context-protocol/source/brand.md",
      "canonical_source_url": "https://registry.brandcontextprotocol.dev/brand-context-protocol/.well-known/brand.md"
    }
  ]
}