Mercury

boundaries.md

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

# Boundaries

> **Public-source demonstration.** These safeguards reflect public Mercury claims and ordinary financial-services caution. Mercury has not reviewed or approved them.

## Financial-services boundaries

```yaml
boundaries:
  - subject: "Company status"
    preference: "Describe Mercury as a fintech company, not an FDIC-insured bank. Name partner banks when discussing banking services."
    source: "https://mercury.com/"
  - subject: "Deposit insurance"
    preference: "Do not state or imply blanket coverage. Preserve eligibility, partner-bank, sweep-network, limit, and failure-of-insured-bank conditions from the current disclosure."
    source: "https://mercury.com/"
  - subject: "Rates, yield, cashback, fees, credit, and pricing"
    preference: "Treat every number as volatile. Recheck the current product page and keep all conditions, dates, and footnotes."
    source: "https://mercury.com/"
  - subject: "Availability and eligibility"
    preference: "Do not imply that every product is available to every company, geography, account type, or applicant."
    source: "https://mercury.com/legal"
  - subject: "Advice"
    preference: "Do not present marketing copy as legal, tax, accounting, investment, or individualized financial advice."
    source: "https://mercury.com/legal"
```

## Mercury Spend boundaries

- Do not say an AI agent independently controls, owns, or authorizes funds.
- Do not say agent cards remove human oversight.
- Describe dedicated agent cards as supporting approved transactions with configured controls and granular visibility.
- Do not invent policy enforcement behavior beyond public examples such as budget routing, categorization, card locks for overdue tasks, and configured rules.
- Do not imply automatic categorization is infallible or eliminates review.
- Do not reproduce demo contact, payment-card, address, or order details visible in product demonstrations.
- Do not present the Simone Bodmer-Turner IO card as generally available without checking current terms and availability.

## Claims and endorsement boundaries

- Mercury has not reviewed or approved this package or the Encoded example.
- Do not describe this Registry publication as official, certified, verified by Mercury, or domain-proven.
- Do not invent customer quotes, savings, approval speed, close-time reduction, fraud outcomes, or compliance outcomes.
- Do not imply that a visual resemblance to mercury.com constitutes Mercury sponsorship.
- Do not use private sales conversations, nonpublic roadmaps, integration timelines, or customer requests as public product claims.

## Escalation topics

Human and current-source review is appropriate for regulated claims, rates, coverage, credit decisions, security incidents, fraud, sanctions, account restrictions, product eligibility, card availability, and any statement that could move money or authorize a transaction.