Operator, Facilitator, or Merchant of Record? The Decision Tree Every Agent Platform Gets Wrong

Three different words get used interchangeably when an agent platform describes who is responsible for sales tax: operator, marketplace facilitator, and merchant of record. They are not synonyms, only one of them is defined in a tax statute, and the one most often relied upon in contracts is the one that decides the least.

This is the post I have been asked for more than any other, and it needs no news hook. The confusion is structural.

Merchant of Record Is Not a Tax Status

A merchant of record is the entity that appears as the seller in the payment rail — the party the card networks hold accountable for the transaction, chargebacks, and refunds. It is a commercial and card-network designation. It is genuinely useful, and platforms like Adyen Agentic have done real work preserving it through agent-led checkout.

What it is not is a term of art in any state sales tax code. No state's collection duty turns on who the card networks treat as the merchant. When a contract says "Platform shall act as merchant of record and shall be responsible for all applicable taxes," that sentence allocates cost between two private parties. It does not transfer a statutory collection obligation, and a state auditor is not a party to it.

The practical consequence: a platform can be the merchant of record and still not be the party a state requires to collect, and — more dangerously — can decline merchant-of-record status and still be a marketplace facilitator by operation of law.

The Statutory Test, and Why It Is Not One Test

Forty-six jurisdictions have marketplace facilitator statutes. They do not share a definition, and the variation is the whole problem.

Missouri takes the narrow, common form. Under RSMo § 144.752(1), a marketplace facilitator is a person that (a) "facilitates a retail sale by a marketplace seller by listing or advertising for sale by the marketplace seller, in any forum, tangible personal property or services that are subject to tax," and (b) "either directly or indirectly through agreements or arrangements with third parties collects payment from the purchaser and transmits all or part of the payment to the marketplace seller." Both prongs are required. Missouri expressly excludes persons who provide only advertising or product listing without touching payment, and excludes third-party financial institutions whose sole activity is processing payments.

Washington is structurally broader. Under WAC 458-20-282(104)(a), a marketplace facilitator is a person that (i) contracts with sellers to facilitate the sale of the seller's products for consideration, (ii) transmits or otherwise communicates the offer or acceptance between buyer and seller, and (iii) engages in any one of seven listed activities: payment processing, fulfillment or storage, listing products, setting prices, branding sales as the facilitator's own, taking orders, or providing customer service.

Read those two side by side with an agent platform in mind. A platform that routes an agent's request to a provider, transmits the acceptance, and sets or displays the price — but never touches money — fails Missouri's payment prong entirely and is not a facilitator there. In Washington it satisfies (i), (ii), and (iii)(D) and is one. Same architecture, opposite answers, and nothing in the contract stack changes either result.

Washington also makes the point explicit that contracts do not control: a standalone payment processor performing no other marketplace function is excluded under WAC 458-20-282(201)(b)(i)(A) regardless of what it has agreed to, and the facilitator's duty to collect under WAC 458-20-282(301)(a) arises from the rule, not from the seller agreement.

The Decision Tree

Work it in this order, per state, per transaction type. The order matters, because the first question that returns "yes" ends the inquiry.

1. Are you selling your own product or service? If the agent output, compute, or API access is yours and you sell it in your own name, you are the retailer. Facilitator law is irrelevant to you. Your question is nexus, and only nexus.

2. Are you buying and reselling in your own name? If you purchase compute or data and resell processed output as your own product, you are the retailer on the outbound leg and a purchaser for resale on the inbound leg. That inbound leg needs a resale certificate. Note that whether an AI agent can hold and present one is not a settled question — no state has addressed it directly — and a buyer who claims resale but consumes the input internally can leave the seller liable. See the Avalara primer on resale certificates for the mechanics.

3. Are you facilitating someone else's sale? Now run each state's actual statutory elements. Not the summary, not the chart — the elements. Ask specifically: do we communicate offer or acceptance? Do we collect and transmit payment? Do we list, price, brand, take orders, or support? Missouri needs listing plus payment. Washington needs contract plus communication plus any one of seven.

4. If none of the above, you are a vendor to the transaction, not a party to it. A pure calculation API or an observability tool sits here.

Merchant of record never appears in this tree. That is the point. It determines who bears the cost between you and your counterparty after the statutory answer is already fixed.

Where the Genuine Uncertainty Sits

I want to be precise about what is settled and what is not. That both prongs of a narrow statute like Missouri's must be met is settled. That contractual labels do not override statutory status is settled.

What is unsettled is where an agent platform that orchestrates without transacting actually lands. Our position is that facilitator obligations should be applied where a state's definition is unambiguously met, and that a pure tax-calculation integration sits outside facilitator classification. That is an interpretation, not a holding. No state has issued guidance on API-only tax platforms and no court has ruled on facilitator classification for agent orchestration. If a state concludes your platform qualifies, you can face liability for uncollected tax alongside your merchants — both parties owing the same underlying tax. Anyone taking the narrow reading should take it knowingly. The Tax Foundation's overview of marketplace facilitator laws is a fair map of how far the definitions range.

What to Do This Week

• Write down which of the four positions you occupy, per state. If you cannot name it, your contracts are carrying weight they cannot hold.

• Stop treating your merchant-of-record clause as a tax answer. Reread it as what it is: an indemnity.

• Run the actual statutory elements in your five largest states rather than a vendor summary chart. The charts flatten exactly the variation that decides your case.

• If you are a marketplace seller on someone else's platform in a facilitator state, confirm that those sales are excluded from your own economic nexus revenue. Double-counting them is the most common quiet error we see.

AgentTax accepts a marketplace_role input of seller, facilitator, or direct and applies each state's facilitator rules accordingly — when you are a seller on a facilitating platform in a facilitator jurisdiction, the transaction is excluded from your nexus revenue and the response flags that the marketplace is the collector of record. See how it works at agenttax.io.

What to Watch

The Multistate Tax Commission's uniformity work is the most likely source of a model facilitator definition that names automated and agent-mediated sales. Nothing in the sections circulated so far does. Watch also for the first state guidance addressing API-only platforms, and for any ruling that tests whether communicating an offer between two machines is "facilitating" within the meaning of a statute drafted for human marketplaces.

This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.