Mercury

values.md

---
bcp_version: "1.1.1"
file_type: values
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
last_updated: 2026-09-23
---

# Values

> **Public-source demonstration.** These principles are inferred from public Mercury product and company material. Mercury has not reviewed or approved them.

## Observed principles

```yaml
values:
  - name: "Clarity over process"
    expression: "Reduce the administrative work around money while keeping decisions and status understandable."
    evidence:
      - "Mercury Spend routes transactions to budgets and presents spend in context."
      - "Mercury describes banking as a source of truth for financial operations."
  - name: "Autonomy with control"
    expression: "Let teams move within a purpose, budget, policy, and permission structure."
    evidence:
      - "Purpose-specific budgets and self-enforcing policies."
      - "Dedicated cards for approved agent transactions with granular visibility."
  - name: "Craft in service of work"
    expression: "Make difficult operational systems feel considered, legible, and humane."
    evidence:
      - "The limited-edition IO card collaboration with Simone Bodmer-Turner."
      - "Public language connecting product form and the act of shaping a business."
  - name: "Specificity earns trust"
    expression: "Describe the mechanism and keep conditions attached to financial claims."
    evidence:
      - "Public product pages explain budgets, locks, rules, categorization, and permissions."
      - "Banking disclosures name partner banks and Mercury's fintech status."
  - name: "Build for ambitious companies"
    expression: "Treat financial operations as enabling infrastructure for people building and scaling companies."
    evidence:
      - "Mercury's About page frames banking as a catalyst rather than an obstacle."
```

## Decision lenses

- If a faster experience would hide control, keep the control visible.
- If a beautiful idea would blur a financial condition, state the condition plainly.
- If an automation claim can name its actual work, name it.
- If agent spend is discussed, show the human-approved purpose and the system's visibility.
- If a claim depends on eligibility, account type, provider, market, or date, keep that qualifier adjacent.

## Sources

- https://mercury.com/about
- https://mercury.com/spend-management
- https://mercury.com/blog/introducing-mercury-spend
- https://mercury.com/legal