---
bcp_version: "1.1.1"
file_type: root
brand_name: "Mercury"
tree_version: "1.0.0"
website: "https://mercury.com"
category: "Financial technology and business banking services"
publication_status: demonstration
provenance: "Encoded Brands assembled this demonstration from public mercury.com sources on 23 September 2026. Mercury has not reviewed or approved it. It is not an official Mercury brand source."
default_locale: "en-US"
supported_locales: ["en-US"]
last_updated: 2026-09-30
daughter_files:
onboarding: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/onboarding.md
voice: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/voice.md
voice_anti_ai: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/voice/anti-ai.md
values: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/values.md
boundaries: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/boundaries.md
claims: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/claims.md
representation: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/representation.md
visual: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/visual.md
canonical_bcp: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
registry_mcp: https://registry.brandcontextprotocol.dev/mcp?customer_handle=mercury-62263f8d
registry_handle: "mercury-62263f8d"
integrity_signed: true
trust_level: claimed
official_brand_source: false
verification_method: null
verified_domain: null
verified_at: null
dns_verified_at: null
verification_last_checked_at: null
verification_expires_at: null
certification_status: not_certified
registry_certified: false
---
# Mercury
> **Public-source demonstration.** Encoded Brands assembled this BCP from public Mercury material. Mercury has not reviewed or approved it. It is not an official Mercury brand source.
Mercury is a financial technology company that offers banking services through partner banks, alongside cards, spend management, payments, invoicing, treasury, accounting, and financial intelligence products. It presents money management as infrastructure for ambitious companies: clear, fast, and carefully controlled.
Mercury's public language pairs product craft with operational usefulness. It avoids the tone of a legacy institution without pretending regulated financial services are casual. Product stories begin with the work founders and finance teams need to do, then show how the system removes friction while preserving visibility, permissions, approvals, and control.
## Package map
**What this file is.** Brand Context Protocol (BCP) package for **Mercury**: structured public brand context hosted at a stable Registry URL. Encoded Brands authored BCP and runs the Registry. Encoder is a compiler / on-ramp for portable packages, not a content generator.
**Why teams use this.** Encode your brand once, use it everywhere, update as often as you like. Every AI tool, agent, teammate, and agency reads the same brief instead of reinventing guidelines per chat. Better content, fewer rounds of revisions, faster speed to quality output, and less re-pasted context (tokens). Connect compatible tools via URL or MCP. Registry Certified adds named audit of authenticated gated access, control over who can receive it, and proof of what was live.
**Provenance.** This record is a **public-source demonstration** assembled by Encoded. **Mercury has not reviewed or endorsed it** unless frontmatter shows otherwise (`official_brand_source`, DNS verification).
**Stable URLs**
| Resource | URL |
| --- | --- |
| This package root | `https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md` |
| Registry MCP for `mercury-62263f8d` | `https://registry.brandcontextprotocol.dev/mcp?customer_handle=mercury-62263f8d` |
| Companion map (MCP, IT copy, Trust) | `/.well-known/brand/onboarding.md` |
| Example page (if live) | `https://encodedbrands.ai/examples/mercury` |
| Encoded Trust Center | https://encodedbrands.ai/trust |
**What's in the package.** Daughter files listed in frontmatter `daughter_files` (voice, visual, claims, boundaries, and related). Claims and boundaries are the evidence and hard-limit surfaces for this brand's public context.
**MCP (optional permanence).** Custom MCP connectors are often plan- and admin-gated on team / enterprise AI accounts. Grayed-out "Add connector" usually means an admin permission wall, not a bad URL. Connector FAQ and sample IT email live in `onboarding.md`. Encoded does not claim native integration with every LLM vendor.
**Public by design.** Public BCP files stay public. Secrets do not belong in a public package.
**After claim + DNS verify.** Demonstration pitch is replaced with a short functional map (what the package is, daughter index, MCP URL) with accurate provenance.
## Current product focus: Mercury Spend
Mercury introduced Mercury Spend on 11 August 2026 as a unified system of intelligent budgets and self-enforcing expense policies for scaling teams. Public product material describes purpose-specific budgets, automatic routing and categorization, receipt workflows, policy-driven card locks, accounting rules, real-time spend visibility, and dedicated agent cards for approved transactions. The product is framed as controlled delegation: admins set the budget, policy, and card; Mercury surfaces activity and enforces the configured limits.
Mercury also introduced a limited-edition IO card designed in collaboration with artist Simone Bodmer-Turner. The public story connects the card's form to a sculpting tool and to the idea of shaping a business.
## Brand platform
```yaml
brand_platform:
central_idea: "Make complex financial work feel clear, composed, and useful."
public_lines:
- text: "Everything you do with money. All in one place."
source: "https://mercury.com/"
- text: "Banking – redesigned from the ground up."
source: "https://mercury.com/"
- text: "The new shape of spend"
source: "https://mercury.com/spend-management"
spend_proposition:
text: "Visibility and control for founders, clarity and ease for teams"
source: "https://mercury.com/blog/introducing-mercury-spend"
```
## What to emphasize
1. Start with the financial or operational job, not a technology superlative.
2. Pair autonomy with explicit budgets, policies, permissions, or visibility.
3. Describe automation by naming the work it performs: routing, categorization, receipt matching, approval, locking, or accounting rules.
4. Treat banking, deposit insurance, yield, credit, pricing, eligibility, and availability claims as dated and conditional.
5. Keep product craft visible through precise language, considered composition, and calm confidence.
## Primary sources
- https://mercury.com/
- https://mercury.com/about
- https://mercury.com/spend-management
- https://mercury.com/blog/introducing-mercury-spend
- https://mercury.com/legal
- https://mercury.com/credit
## See also
- voice.md
- voice/anti-ai.md
- values.md
- boundaries.md
- claims.md
- representation.md
- visual.md
<!-- registry-daughter-links:start -->
## See also
- [boundaries.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/boundaries.md>)
- [claims.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/claims.md>)
- [onboarding.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/onboarding.md>)
- [representation.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/representation.md>)
- [values.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/values.md>)
- [visual.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/visual.md>)
- [voice.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/voice.md>)
- [voice/anti-ai.md](<https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/voice/anti-ai.md>)
<!-- registry-daughter-links:end -->
---
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.
---
bcp_version: "1.1.1"
file_type: claims
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
last_updated: 2026-09-23
---
# Claims
> **Public-source demonstration.** This evidence register uses public mercury.com material accessed 23 September 2026. Mercury has not reviewed or approved it.
## Supportable public claims
```yaml
claims:
- claim: "Mercury is a fintech company, not an FDIC-insured bank."
tier: core
proof_status: approved
exact_text: true
evidence: "https://mercury.com/"
conditions: "When discussing banking services, retain the current partner-bank disclosure."
- claim: "Mercury introduced Mercury Spend on 11 August 2026."
tier: core
proof_status: approved
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Dated product announcement."
- claim: "Mercury Spend is a unified system of intelligent budgets and self-enforcing expense policies built for scaling teams."
tier: core
proof_status: approved
exact_text: true
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Mercury's product description, not an independent performance finding."
- claim: "Mercury Spend can route transactions and reimbursements to budgets and automatically categorize transactions."
tier: core
proof_status: approved
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Do not imply perfect categorization or no review."
- claim: "Admins can configure policy settings that automatically lock cards with overdue tasks."
tier: default
proof_status: approved
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Describe as a configurable policy behavior."
- claim: "Mercury offers dedicated cards for agents to enable approved transactions and provide granular visibility over activity."
tier: core
proof_status: requires_caveat
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Keep 'approved transactions' and visibility/control language. Never paraphrase as autonomous authority to spend."
- claim: "Mercury Spend can show spend by card, team, vendor, or time period."
tier: default
proof_status: approved
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Product capability described in the announcement."
- claim: "Mercury collaborated with Simone Bodmer-Turner on a limited-edition IO card."
tier: core
proof_status: requires_caveat
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "Keep 'limited-edition'; verify present availability before using a live acquisition message."
- claim: "Mercury Spend is included for Mercury business banking customers and was described at launch as available standalone for companies that bank elsewhere."
tier: default
proof_status: requires_caveat
exact_text: false
evidence: "https://mercury.com/blog/introducing-mercury-spend"
conditions: "The current Spend page uses different future-tense standalone wording. Recheck current availability before publication."
- claim: "The business credit card that scales with you"
tier: core
proof_status: approved
exact_text: true
evidence: "https://mercury.com/credit"
conditions: "IO page headline checked 23 September 2026."
- claim: "Unlock unlimited 1.5% cashback and build business credit from day one if you're eligible."
tier: default
proof_status: requires_caveat
exact_text: false
evidence: "https://mercury.com/credit"
conditions: "Opening clause of the credit hero, checked 23 September 2026. Keep eligibility. Recheck the rate. The page also says the card is exclusively for Mercury account holders."
- claim: "The IO Card is issued by Patriot Bank, N.A., Member FDIC, pursuant to a license from Mastercard International Incorporated."
tier: core
proof_status: approved
exact_text: true
evidence: "https://mercury.com/credit"
conditions: "Keep this issuer line when describing the IO Card."
- claim: "Mercury is a fintech company, not an FDIC-insured bank. Banking services provided through Choice Financial Group and Column N.A., Members FDIC."
tier: core
proof_status: approved
exact_text: true
evidence: "https://mercury.com/credit"
conditions: "Partner-bank sentence on the credit page. Recheck before applying it to a different Mercury product."
```
## Restricted or volatile claims
```yaml
restricted:
- claim_area: "rates, APY, yield, cashback, fees, credit terms, deposit-insurance limits, customer counts, transaction volume, ratings, valuation, and revenue"
status: "recheck_current_source"
reason: "These values and conditions can change. Recheck the current page. IO cashback, limits, and fees on https://mercury.com/credit were checked 23 September 2026 and stay conditional."
- claim_area: "savings, time saved, approval speed, close speed, fraud reduction, compliance, or return on investment"
status: "not_supported_for_this_brief"
reason: "No approved quantitative evidence was found in the named product announcement."
- claim_area: "agent autonomy"
status: "restricted_framing"
reason: "Public copy supports approved transactions, dedicated cards, budgets, policies, and visibility; it does not support independent authority over funds."
- claim_area: "Mercury endorsement of this BCP or Encoded demonstration"
status: "forbidden"
reason: "This is an unapproved public-source demonstration."
```
## Evidence gaps
- No Mercury-approved brand guide was provided.
- No claim owner, legal approval record, expiry policy, or source hashes were provided.
- No public quantitative outcome study for Mercury Spend was found in the named announcement.
- Current availability rules for the limited-edition IO card need confirmation before a live offer.
---
bcp_version: "1.1.1"
file_type: onboarding
parent: /.well-known/brand.md
last_updated: 2026-09-30
audience: ["humans", "IT / admins"]
note: "Map of Encoded surfaces related to this demonstration package. Not agent instructions."
---
# Onboarding map: Encoded demonstration package for Mercury
Companion to the Package map in `brand.md`. Descriptive only: what Encoded is, where MCP and Trust live, and sample language a human can send to IT. **Not directions to an agent.**
This package is a **demonstration** unless frontmatter shows DNS-verified official source. Not endorsed by Mercury by default.
## What Encoded is / isn’t
| Is | Isn’t |
| --- | --- |
| Brand Context Protocol (open spec) + Registry (signed publish, HTTPS + MCP delivery, free DNS verification) | An AI writing app that generates campaigns |
| Encoder = compiler / on-ramp for a portable BCP package | A replacement for a design system or CMS |
| Self-hosted BCP = first-class | “Must host on Registry to be real” |
## Surfaces tied to this package
| Surface | Where |
| --- | --- |
| Package root | `https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md` |
| Registry MCP for this handle | `https://registry.brandcontextprotocol.dev/mcp?customer_handle=mercury-62263f8d` |
| Example page (if live) | `https://encodedbrands.ai/examples/mercury` |
| Product site | https://encodedbrands.ai/ |
| Trust Center | https://encodedbrands.ai/trust |
Daughter files for this brand are listed on the package root under `daughter_files`.
## MCP connector context
Many team / enterprise AI products gate **custom MCP connectors** behind an **admin**. Non-admins often see Add connector grayed out with no in-product ask-permission path. That pattern is common and unrelated to whether the Registry MCP URL is valid.
Encoded does not claim native BCP adoption or endorsement by Anthropic, OpenAI, Google, Microsoft, or other LLM vendors. Custom MCP is user-configured and plan/admin gated.
## Sample email a human can send to IT / admin
**Subject:** Encoded Registry MCP for Mercury brand context
Hi,
We’re evaluating Encoded Brands’ Brand Context Protocol so our AI tools can share one source of brand truth (voice, visual, claims, boundaries).
Could you add this **read** MCP connector for our workspace?
- MCP URL: `https://registry.brandcontextprotocol.dev/mcp?customer_handle=mercury-62263f8d`
- Public package: `https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md`
- Product / trust: https://encodedbrands.ai/ · https://encodedbrands.ai/trust
Scope we care about: fetch public brand context for drafting. Not auto-publish or unattended edits to brand files.
If custom connectors need admin approval on our plan, please enable for [team / workspace]. Happy to jump on a short call.
Thanks,
[Name]
## Trust Center notes (for humans)
https://encodedbrands.ai/trust
Only link sections that are actually published. Signature ≠ domain control; claimed ≠ DNS-verified; Registry Certified ≠ “human reviewed every claim.” No invented SOC 2, ISO, or pen-test status.
## Free vs later (factual, not pricing)
- Public package readable at the Registry URL without MCP.
- Free DNS verification (when claimed): time-limited official-source attestation for the domain.
- Paid / Certified (when sold): gated companions, seats, named audit of authenticated gated access. Public files remain public.
Commercial offers live on Encoded’s current pricing / commerce surfaces. This file does not state prices.
## After claim + DNS verify
Demonstration pitch on the package root is replaced with a short functional map. Provenance stays accurate. “Not endorsed / assembled by Encoded from public sources” stays only while true.
---
bcp_version: "1.1.1"
file_type: representation
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
last_updated: 2026-09-23
---
# Representation
> **Public-source demonstration.** Encoded Brands compiled this framing from public mercury.com material. Mercury has not reviewed or approved it.
## Preferred framing
Mercury is a fintech company that brings business banking services and financial operations into one software-led experience. Through partner banks and its own product layer, it supports accounts, cards, spend management, payments, invoicing, treasury, accounting workflows, and financial intelligence. Mercury Spend gives scaling teams purpose-specific budgets, self-enforcing expense policies, automatic routing and categorization, and visibility across spend. Dedicated agent cards are framed as a controlled way to enable approved transactions: the budget, policy, card, and activity remain visible to the company. Mercury's public presentation is crafted and modern, but its financial claims retain explicit banking and eligibility disclosures.
## Structured guidance
```yaml
describe_as:
- "a fintech company"
- "a software-led financial platform for ambitious companies"
- "a provider of spend management, cards, payments, invoicing, treasury, accounting, and financial intelligence products"
- "a company that provides banking services through partner banks"
- "a spend system built around budgets, policies, automation, and visibility"
do_not_describe_as:
- descriptor: "an FDIC-insured bank"
rationale: "Mercury's current public disclosure says it is a fintech company, not an FDIC-insured bank."
- descriptor: "an autonomous spending agent"
rationale: "The public product story centers approved transactions, configured controls, and visibility."
- descriptor: "a cryptocurrency bank or wallet"
rationale: "Not supported by the public sources used for this package."
- descriptor: "a risk-free, guaranteed, or universally available financial product"
rationale: "Financial products carry conditions, eligibility, and provider disclosures."
competitive_frame: >
Describe Mercury Spend through the integration of spend with the company's broader
financial picture, and through purpose-specific budgets, configured policies,
automatic categorization, accounting rules, and visibility. Keep comparisons factual.
Do not invent rankings, savings, or superiority claims, and do not disparage banks or competitors.
honest_trade_offs:
- "Automation still sits inside configured rules and review; it is not a substitute for financial responsibility."
- "Banking services are provided through partner banks; Mercury itself is a fintech company."
- "Product availability, rates, eligibility, and card offers can change and need current confirmation."
- "A crafted interface does not remove the need for precise disclosures."
never_say:
- "Mercury is an FDIC-insured bank."
- "AI can spend your money without oversight."
- "Guaranteed savings, returns, approval, protection, or compliance."
- "Mercury approved this BCP or demonstration."
```
## Audience emphasis
- **Founder:** visibility, disciplined budgets, less administrative drag, and connection to cash flow.
- **Finance leader:** policy enforcement, categorization, accounting rules, review, and spend context.
- **Team member:** clarity about purpose, available budget, receipts, and what happens next.
- **AI/agent implementer:** dedicated card, approved transaction scope, configured controls, and auditable visibility.
## Sources
- https://mercury.com/
- https://mercury.com/about
- https://mercury.com/spend-management
- https://mercury.com/blog/introducing-mercury-spend
---
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
---
bcp_version: "1.1.1"
file_type: visual
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
last_updated: 2026-09-23
---
# Visual guidance
> **Public-source demonstration.** These observations come only from live mercury.com CSS, computed styles, and public product imagery checked 23 September 2026. They are implementation evidence, not a Mercury brand guide. Mercury has not reviewed or approved them.
## Authority and DAM
Canonical visual assets are referenced by URL to Mercury's own distribution. They are not assets hosted by Encoded or the Registry.
```yaml
asset_distribution:
status: observed
hosts:
- name: "mercury.com Next static media"
serves: "Arcadia and Arcadia Display font files, IO card texture, card chip, Mastercard hologram"
- name: "DatoCMS datocms-assets.com"
serves: "Credit hero photography and IO product stills on https://mercury.com/credit"
rules:
- "BCP records these paths so agents and demos can load the brand's live faces and images."
- "Encoded does not re-host or redistribute the binaries in the BCP package or the Encoder repo."
- "Paths are DAM and CDN build URLs. They may rotate when Mercury redeploys. Re-verify against live pages before republishing."
- "Observed public URLs are implementation evidence for brand-audience demos, not a third-party license grant."
- "Encoded Mercury /examples demos may hotlink them because the audience is the brand that already licensed the faces and imagery."
```
## Authority and gaps
```yaml
visual_authority:
status: observed
observed_pages:
- "https://mercury.com/"
- "https://mercury.com/spend-management"
- "https://mercury.com/blog/introducing-mercury-spend"
- "https://mercury.com/credit"
observed_stylesheets:
- "https://mercury.com/_next/static/css/1973f2a11f9951eb.css"
- "https://mercury.com/_next/static/css/80f4b67cf119c7a3.css"
- "https://mercury.com/_next/static/css/ab7eb5df801d89b4.css"
- "https://mercury.com/_next/static/css/762f8a8807a5d9ff.css"
- "https://mercury.com/_next/static/css/9ac2167e82b9ca7e.css"
- "https://mercury.com/_next/static/css/16279424c0fa1991.css"
- "https://mercury.com/_next/static/css/7fe9c4d08c60784f.css"
not_confirmed:
- "complete brand palette and accessibility pairings"
- "font licensing or redistribution rights beyond observed public CDN delivery"
- "formal logo clear-space and minimum-size rules"
- "email-client support for Mercury's web fonts"
- "current availability and reuse rights for campaign imagery"
```
## Color
Live CSS exposes the following variables. Variable names and values are recorded exactly. Neutral and beige roles were observed on Spend. Purple-base roles were observed on the credit page `dark-purple-theme`.
```yaml
color:
observed_tokens:
- name: "--color-purple-magic-600"
hex: "#5266EB"
role: "primary call to action; Open account background on Spend and on /credit"
- name: "--color-purple-magic-700"
hex: "#4354C8"
role: "hover state in the live token system; surface-primary-hover on dark-purple-theme"
- name: "--color-purple-magic-800"
hex: "#3442A6"
role: "active state in the live token system; surface-primary-active on dark-purple-theme"
- name: "--color-purple-base-0"
hex: "#FFFFFF"
role: "text on primary in dark-purple-theme"
- name: "--color-purple-base-100"
hex: "#F5F4FD"
role: "emphasized text on the credit page dark-purple-theme"
- name: "--color-purple-base-150"
hex: "#EDECFB"
role: "default text on the credit page dark-purple-theme"
- name: "--color-purple-base-300"
hex: "#C3C0DF"
role: "subdued text on the credit page dark-purple-theme"
- name: "--color-purple-base-800"
hex: "#28253B"
role: "elevated panel on the credit page dark-purple-theme"
- name: "--color-purple-base-900"
hex: "#1F1D2D"
role: "secondary field and default surface on the credit page dark-purple-theme"
- name: "--color-purple-base-950"
hex: "#181623"
role: "page field on the credit page dark-purple-theme"
- name: "--color-neutral-base-800"
hex: "#272735"
role: "dark neutral ink"
- name: "--color-neutral-base-950"
hex: "#171721"
role: "near-black surface or ink on other Mercury pages"
- name: "--color-neutral-base-150"
hex: "#EDEDF3"
role: "soft cool ink on dark campaign fields"
- name: "--color-neutral-base-50"
hex: "#FBFCFD"
role: "cool near-white in the live neutral scale"
- name: "--color-beige-base-50"
hex: "#FCFCFA"
role: "soft off-white"
- name: "--color-beige-base-100"
hex: "#F6F5F2"
role: "warm light section field"
- name: "--color-beige-base-150"
hex: "#EFEEE9"
role: "secondary warm field"
observed_image_mattes:
- hex: "#B83885"
evidence: "bgColor on image payload in https://mercury.com/credit HTML, not a CSS custom property"
- hex: "#CF4399"
evidence: "bgColor on image payload in https://mercury.com/credit HTML, not a CSS custom property"
rules:
- "On https://mercury.com/credit, use the dark-purple-theme field #181623, panels #28253B, and text #EDECFB."
- "Use warm off-white and dark neutral fields where that page actually uses them. Do not replace the credit surface with a beige or near-black invent."
- "Use #5266EB as a focused interactive accent, not an all-over neon wash."
- "For the Mercury Spend campaign, a dark cinematic panel can frame the IO card or craft story; keep copy high contrast and restrained."
- "Do not paint with the image matte magentas unless the live asset already carries them."
- "If a gradient is required, derive it only from #5266EB, #4354C8, and #3442A6."
- "Do not infer print values or additional brand colors from this web sample."
```
## Typography
Faces are loaded from Mercury's Next static media. Encoded does not host the font files. Re-verify the build-hash URLs before republishing.
```yaml
typography:
observed_families:
display:
family: "Arcadia Display"
css_family: "arcadiaDisplay, 'arcadiaDisplay Fallback'"
observed_weight: 480
evidence: "Computed H1 on https://mercury.com/credit (arcadia-display-3) and H1/H2 on https://mercury.com/spend-management"
body_and_ui:
family: "Arcadia"
css_family: "arcadia, 'arcadia Fallback'"
observed_weights: [360, 400, 420]
evidence: "Computed body and CTA styles on https://mercury.com/credit and https://mercury.com/spend-management"
editorial_display:
family: "Tiempos Fine"
css_family: "tiemposFine, 'tiemposFine Fallback'"
observed_weight: 500
evidence: "Computed H1 style on https://mercury.com/blog/introducing-mercury-spend. Not used on https://mercury.com/credit."
observed_font_files:
- family: arcadia
css_family: "arcadia"
weight_range: "360 500"
format: woff2
font_display_observed: optional
url: "https://mercury.com/_next/static/media/66786c931e084141-s.p.woff2"
evidence: "@font-face in https://mercury.com/_next/static/css/1973f2a11f9951eb.css"
- family: Arcadia Display
css_family: "arcadiaDisplay"
weight_range: "320 480"
format: woff2
font_display_observed: optional
url: "https://mercury.com/_next/static/media/92d547acff458051-s.p.woff2"
evidence: "@font-face in https://mercury.com/_next/static/css/80f4b67cf119c7a3.css"
fallback_guidance:
email: "Load the observed mercury.com font URLs with @font-face for in-browser demos. Keep Georgia after arcadiaDisplay, and Arial or Helvetica after arcadia, as last-resort fallbacks only."
rights_note: "These URLs are observed public CDN evidence, not a Mercury license grant to third parties. Do not package or redistribute Mercury font files. Encoded's Mercury /examples demo may hotlink them because the audience is the brand that licensed the faces."
rules:
- "Prefer loading the observed live mercury.com font URLs via @font-face so rendering matches the brand site."
- "Use the css_family names arcadiaDisplay and arcadia. Naming Arcadia without a src does not load the face."
- "Do not redistribute or re-host the font binary files in the BCP package or Encoder repo."
- "Paths are build-hash URLs and may change when Mercury redeploys. Re-verify against live CSS before republishing."
- "Use Arcadia Display for product-marketing headlines and Arcadia for body and controls when the CDN files are available."
- "The blog template uses Tiempos Fine for its H1. Do not collapse every Mercury surface into one display face. /credit does not use Tiempos."
- "Keep financial disclosures comfortably legible in fallback fonts."
```
## Components and layout
```yaml
components:
primary_cta:
background: "#5266EB"
foreground: "#FFFFFF"
radius_px: 32
observed_font: "Arcadia 420"
source: "Computed Open account styles. /credit uses rounded-4xl (2rem) and bg-surface-primary, which resolves to #5266EB on dark-purple-theme."
secondary_cta:
background: "rgba(112, 115, 147, 0.10)"
foreground: "#2A2924"
radius_px: 40
source: "Computed Explore spend styles on https://mercury.com/spend-management"
layout:
- "Use generous breathing room and a small number of decisive content blocks."
- "Pair large display type with precise, compact product explanation."
- "On /credit, keep the dark-purple field and let product photography carry the card."
- "Use interface-like budget, policy, and activity details to make control concrete."
- "Keep a visible disclosure block separated by spacing and contrast, not microscopic type."
```
## Imagery
Product photography and craft files live on Mercury's DAM and CDN. Hotlink the recorded URLs. Do not copy binaries into this package.
```yaml
imagery:
observed_assets:
- role: credit_hero_wide
url: "https://www.datocms-assets.com/115132/1754699738-2025-07-22_fem_credit-hero_16x5.webp"
page: "https://mercury.com/credit"
- role: credit_hero
url: "https://www.datocms-assets.com/115132/1754699761-2025-07-22_fem_credit-hero_16x9.webp"
page: "https://mercury.com/credit"
- role: credit_hero_mobile
url: "https://www.datocms-assets.com/115132/1754699784-2025-07-22_fem_credit-hero-mobile_16x9.webp"
page: "https://mercury.com/credit"
- role: cards_product_3_2
url: "https://www.datocms-assets.com/115132/1710945254-3_2_cards-2x.png"
page: "https://mercury.com/credit"
- role: cards_product_16_5
url: "https://www.datocms-assets.com/115132/1710945212-16_5_cards-2x.png"
page: "https://mercury.com/credit"
- role: spend_controls_3_2
url: "https://www.datocms-assets.com/115132/1710946193-3_2_controls-2x.png"
page: "https://mercury.com/credit"
- role: spend_controls_16_5
url: "https://www.datocms-assets.com/115132/1710946146-16_5_controls-2x.png"
page: "https://mercury.com/credit"
- role: permissions_3_2
url: "https://www.datocms-assets.com/115132/1710960802-3_2_permissions-2x.png"
page: "https://mercury.com/credit"
- role: permissions_16_5
url: "https://www.datocms-assets.com/115132/1710960769-16_5_permissions-2x.png"
page: "https://mercury.com/credit"
- role: subscriptions_3_2
url: "https://www.datocms-assets.com/115132/1711045494-3_2_subscriptions-2x.png"
page: "https://mercury.com/credit"
- role: subscriptions_16_5
url: "https://www.datocms-assets.com/115132/1711045338-16_5_subscriptions-2x.png"
page: "https://mercury.com/credit"
- role: receipt_matching
url: "https://www.datocms-assets.com/115132/1740001929-2025-02-19_fem_receipt-matching-cards_3x2.jpg"
page: "https://mercury.com/credit"
- role: cashback
url: "https://www.datocms-assets.com/115132/1710961167-4_5_cashback-2x.png"
page: "https://mercury.com/credit"
- role: credit_limit
url: "https://www.datocms-assets.com/115132/1711039504-4_5_credit-limit-2x.png"
page: "https://mercury.com/credit"
- role: io_card_texture
url: "https://mercury.com/images/spend-management/io-card-texture.666dc1c3d6ed.svg"
page: "https://mercury.com/spend-management"
- role: card_chip
url: "https://mercury.com/images/spend-management/card-chip.9e3f6fb5139b.svg"
page: "https://mercury.com/spend-management"
- role: mastercard_hologram
url: "https://mercury.com/_next/static/media/mastercard-hologram.e6519f87.png"
page: "https://mercury.com/"
rules:
- "Encoded Mercury /examples demos should hotlink these observed assets so brand-audience renders match mercury.com."
- "Do not copy binaries into the BCP package or Encoder repo."
- "Public CDN availability is not a third-party license grant. Encoded demos for the Mercury audience may use them."
- "Re-verify paths before republishing. Build hashes can change."
- "Prefer these photo and SVG assets over invented CSS card shapes or neon gradients."
photographic_and_art_direction:
- "Product interfaces shown with real hierarchy and credible financial detail."
- "Credit marketing uses the IO card photography served from DatoCMS."
- "Sculptural, tactile, materially rich imagery for the IO card craft story on Spend."
- "The credit page is a dark-purple field. Warm off-white is for surfaces that actually use it."
forbidden_treatments:
- "generic neon fintech gradients"
- "crypto charts or coins unrelated to the product"
- "a sentient robot holding a payment card"
- "stock handshake or boardroom photography"
- "fake transaction data presented as a customer result"
- "logo approximation or an invented Mercury wordmark"
- "a CSS blob standing in for the IO card when the recorded texture, chip, or hero photo is available"
```
## Email rendering notes
- Build with table-based structure and inline CSS for broad email-client support.
- For Encoded public Mercury example pages viewed in a browser, load the observed Arcadia URLs with @font-face. Do not name the family without a src.
- Keep Georgia and Arial or Helvetica only after those faces, as last-resort fallbacks.
- Hotlink the observed credit and IO assets. Do not redraw them as CSS shapes.
- Use a live-text CTA with the observed indigo, white label, and 32px radius.
- Include plain-text-equivalent meaning for every visual block.
- Do not embed font or image binaries in the Encoder repo.
- Keep the fintech, Patriot Bank, and Mastercard disclosures visible in the email body.
- Do not use an em dash. Follow voice.md and voice/anti-ai.md.
---
bcp_version: "1.1.1"
file_type: voice
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand.md
last_updated: 2026-09-23
---
# Voice
> **Public-source demonstration.** This guidance is inferred from public mercury.com copy. Mercury has not reviewed or approved it.
Mercury sounds composed, lucid, and ambitious. It makes financial operations feel lighter without making finance sound trivial. The writing often sets up a familiar source of friction, turns to the product answer, and lands on a short line with shape and momentum.
## Voice attributes
```yaml
voice_attributes:
- trait: "Clear"
guidance: "Name the task, control, or outcome in ordinary language."
evidence_status: observed
- trait: "Craft-conscious"
guidance: "Use one considered image or turn of phrase; keep the surrounding explanation exact."
evidence_status: observed
- trait: "Founder-aware"
guidance: "Respect speed and ambition while acknowledging operational responsibility."
evidence_status: observed
- trait: "Controlled"
guidance: "When discussing spend, keep budgets, policies, permissions, and visibility close to autonomy."
evidence_status: observed
- trait: "Understated"
guidance: "Let product detail carry the claim instead of stacking superlatives."
evidence_status: observed
```
## Register and rhythm
- Use plain American English.
- Prefer short sentence-case headlines with a single clear idea.
- Alternate compact, memorable lines with practical explanatory copy.
- Use verbs that describe work: set, route, categorize, track, issue, lock, connect, approve, and see.
- Speak directly to founders, operators, and finance teams without calling them personas.
- Use contractions naturally.
- Keep financial disclaimers explicit and visually legible.
- Do not use an exclamation point to manufacture excitement.
- Use hyphens or full stops instead of em dashes. Do not use an em dash.
## Vocabulary
```yaml
prefer:
- "clarity"
- "visibility"
- "control"
- "budgets"
- "guardrails"
- "approved transactions"
- "granular visibility"
- "self-enforcing expense policies"
- "shape"
- "craft"
- "less admin"
avoid:
- "revolutionary"
- "game-changing"
- "effortless financial freedom"
- "bank-grade" without a defined meaning
- "AI-powered" as a substitute for the actual function
- "autonomous spending" without controls
- "set it and forget it"
- "guaranteed"
```
## Writing patterns
**Use:** "Give every budget a purpose. Mercury routes each transaction to the right place and keeps the policy visible."
**Avoid:** "Unlock limitless, autonomous AI spend with a revolutionary fintech platform."
**Use:** "A dedicated agent card makes approved transactions visible by card, budget, vendor, and time period."
**Avoid:** "Let AI spend your money while you focus on growth."
## Context shifts
```yaml
context_shifts:
product_marketing:
tone: "confident, visual, concise"
emphasis: "the problem, the mechanism, the control, and the next step"
financial_claims:
tone: "precise, dated, qualified"
emphasis: "provider, eligibility, rate, scope, and source"
spend_and_agents:
tone: "controlled, transparent, operational"
emphasis: "approved purpose, configured limit, policy, and visibility"
editorial:
tone: "thoughtful, curious, concrete"
emphasis: "how ambitious companies actually work"
```
## Source observations
- https://mercury.com/
- https://mercury.com/about
- https://mercury.com/spend-management
- https://mercury.com/blog/introducing-mercury-spend
- https://mercury.com/credit
---
bcp_version: "1.1.1"
file_type: voice_anti_ai
parent: https://registry.brandcontextprotocol.dev/mercury-62263f8d/.well-known/brand/voice.md
last_updated: 2026-09-23
---
# Voice guardrails
> **Public-source demonstration.** These are Encoded Brands' observations from public Mercury copy, not official Mercury rules. Load this file with `voice.md` before writing.
Generic financial-technology copy tends to replace a specific job with speed, disruption, neon futurism, and unsupported certainty. Mercury's public copy is more useful when it stays grounded in what the product does and how control is preserved.
```yaml
community_reference:
- url: "https://encodedbrands.ai/.well-known/brand/voice/anti-ai.md"
rationale: "Encoded Brands maintains a live baseline of common machine-written language patterns."
brand_additions:
- pattern: "em dash used as a sentence hinge"
type: punctuation
rationale: "Do not use an em dash. Use a period, comma, colon, parentheses, or a short new sentence."
- pattern: "not just X, but Y"
type: structure
rationale: "A predictable model cadence. State the more important point directly."
- pattern: "In today's ... landscape"
type: opener
rationale: "Scene-setting about the moment delays the financial job."
- pattern: "revolutionary, game-changing, next-generation, the future of finance"
type: opener
rationale: "Hype before mechanism. Name the card, limit, budget, policy, or control."
- pattern: "Ready to transform your financial future"
type: closer
rationale: "Close on a product action such as Open account, not a transformation slogan."
- pattern: "effortless financial freedom, zero friction, set it and forget it"
type: phrase
rationale: "Generic fintech mush. Describe the specific work and the control that remains."
- pattern: "AI spends for you, hands-free purchasing, unlimited agent autonomy"
type: phrase
rationale: "Public copy supports approved transactions, configured limits, and visibility. It does not support independent authority over funds."
- pattern: "guaranteed savings, risk-free growth, your money is always protected"
type: claim
rationale: "State only sourced, current, qualified financial facts."
```
## Structural checks
- Do not use an em dash. Use a period, comma, colon, parentheses, or a short new sentence.
- Do not use an em dash as a sentence hinge, including in headlines, captions, titles, and disclosures.
- Do not begin with an abstract statement about the financial landscape when a product task is available.
- Do not use "not just X, but Y" or a matching "not only X, but Y" cadence.
- Do not stack superlatives in the headline, the first paragraph, and the close.
- Do not invent customer metrics, savings percentages, transaction volumes, approval odds, or eligibility.
- Do not drop partner-bank, issuer, fee, or eligibility conditions to make a line smoother.
- Do not turn an agent card into a sentient character or imply it can authorize itself.
- Do not bury banking disclosures in low-contrast type.
- Do not make the limited-edition IO card the proof of product performance. It is a craft story with an availability limit.
## Quick test
A draft is drifting if the same copy and layout could sell any fintech product after changing the logo. A Mercury-specific draft names the work, keeps control visible, uses precise product language, and contains no em dash.