Brand Context Protocol

ACME Corporation

Commerce

Brand-domain control is not verified; this record is not attested as an official brand publication.

12 published files · BCP source version 2.0.0 · Publication cc869ddaeec43f5fd85a4523e12f95df0860818df815ba9d13de2f3df12396d4 · Revision b43f8152-e618-4646-b72a-c844d2a00e9c

HTML and aggregate JSON are readable representations. Each document links to its signed canonical source.

Using this BCP with your AI · Current Registry help, separate from the published files.

Commerce

Read this sectionJSONMarkdown sourceSigned canonical source
---
bcp_version: "2.0.0"
file_type: commerce
parent: /.well-known/brand.md
brand_name: "ACME Corporation"
last_updated: "2026-10-12"
---

# Commerce

This fictional ACME package includes illustrative commerce locations. This file is a signpost, not a checkout or authorization to transact. Host policy and user authorization govern any use of external payment protocols.

```yaml
understand_first: >
  Read /.well-known/brand.md and the claims, boundaries, and representation
  daughter files before purchasing or transacting on ACME's behalf.

offers:
  - id: widget-pro
    name: "Widget Pro"
    summary: "The flagship widget, billed monthly."
    price: { amount: 49.00, currency: USD, interval: month }
    terms_url: "https://acme.example.com/terms"

# Most-preferred protocol first. A consuming agent selects the first entry it
# can transact over and ignores the rest. BCP defines none of these payment
# flows itself; it points to them.
protocols:
  - protocol: ucp
    profile: "https://acme.example.com/.well-known/ucp"
  - protocol: mpp
    endpoint: "https://api.acme.example.com/agent/checkout"
    challenge: 402
    credential_header: "Authorization: Payment <token>"
```