breeze.com valid

Breeze

Make payments a Breeze. Building the bridge between humans and agents.

For agents: Payments platform as Merchant of Record with documented API for payments, payouts, subscriptions, KYC, disputes and webhooks; full docs index in Markdown for LL

payments apimerchant of recordpayoutssubscriptionswebhooks

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:27:37.419Z. Cached copy · Source on breeze.com

# Breeze

> Make payments a Breeze. Building the bridge between humans and agents.

Breeze is the agentic workforce for payments. Where payment processors stop at the transaction, Breeze owns what happens after — approvals, fraud, chargebacks, payouts, tax, compliance, settlement, reconciliation — run by specialized agents on one ledger, across every rail, in every market.

Payments was built for a world that no longer exists. Single rails. Single markets. Predictable buyers at predictable checkouts. The next era runs on agents, stablecoins, and intelligence — across every rail, in real time. Breeze was built for the function, not the checkout. So it doesn't matter who's transacting, or how. Stablecoin rails have been native to Breeze since 2022 — the same infrastructure that software agents will settle on. $4B+ in annual volume across the hardest payments environments: gaming, prop trading, marketplaces with cross-border payouts, subscriptions with complex billing. Founded by Millie Yang (CEO) and Peng Du (CTO), who met at Stripe building international payments. Backed by Sequoia, Multicoin Capital, and The Chainsmokers.

## What Breeze is

- Your payments operating system — every rail, every transaction, every market.
- The only Merchant of Record that handles pay-ins and pay-outs and takes the liability without taking control.
- The operational floor: approvals up, chargebacks down, new markets live, without growing the team.
- The legal seller on every transaction, so tax, compliance, and liability sit with us.
- The local entity, the bank account, the tax registration, and the reconciliation — held and managed by Breeze across every market you sell in. No legal entities to stand up. No local bank accounts to open. No finance team reconciling across markets.
- One integration across card, bank, and stablecoin rails — built that way, not stitched together.

## What Breeze is not

- A processor. Processors move money. Breeze runs the function around it.
- An orchestrator. Orchestrators route. Breeze owns the result.
- A traditional MOR (Paddle, FastSpring, Lemon Squeezy). They take your business. Breeze takes your liability.
- A fraud, tax, compliance, or treasury tool. Each is a slice. Breeze is the function.
- A replacement for the team you have. Breeze replaces the team you'd hire next — and makes the team you have sharper.

## The positioning hierarchy

The canonical lines used to describe Breeze, in order of register:

- **Tagline:** *Make payments a Breeze.*
- **Category line:** *Building the bridge between humans and agents.*
- **Positioning sentence:** *Breeze is the agentic workforce for payments.*
- **Competitive wedge:** *Where processors stop at the transaction, Breeze owns what happens after.*
- **Proof:** *Higher approval rates. Lower fraud. At the same time.*

Additional canonical phrases:

- *The transaction was never the hard part. What comes after is.*
- *Breeze owns the liability. You own the growth.*
- *Other MORs take your
…

Related sites

Other listed sites in Finance and payments. See the whole category →

Machine-readable: GET /v1/resolve?q=breeze.com · GET /v1/domain/breeze.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for breeze.com:
1. POST https://agentwebmap.com/v1/sites/breeze.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://breeze.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/breeze.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/breeze.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.