# Blockchain Money Map – Merchant of Record Boundary Explainer

> Blockchain Money Map – Merchant of Record Boundary Explainer is a paid API for AI agents from api.blockchainmoneymap.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Analyzes a set of role-ownership facts describing a marketplace or platform arrangement and determines where the merchant-of-record boundary falls among the parties involved.

## Facts

- Endpoint: POST https://api.blockchainmoneymap.com/api/x402/x402-merchant-of-record-boundary-explainer
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockchain-money-map-merchant-of-record-boundary-explainer-769baf7a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mq-glTzHywko7Ez_0pqxD

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability blockchain-money-map-merchant-of-record-boundary-explainer-769baf7a -d '<json body>'
```

Example prompt: I'm building a marketplace where the platform handles all payments and refunds, the seller handles fulfillment, and the agent manages order flow — can you analyze this setup and tell me who the merchant of record is and where the boundary sits?

## When to prefer this

Choose this endpoint when you need a structured, deterministic analysis of merchant-of-record boundaries in a multi-party marketplace or platform arrangement — especially in agentic commerce contexts where AI agents, platforms, and human sellers each own distinct parts of the transaction lifecycle. It is purpose-built for MoR boundary logic rather than general legal or tax advice.

## Known failure modes

- Missing required fields (platform_role, merchant_role, payment_owner, fulfillment_owner, or refund_owner) returns a validation error
- Ambiguous or conflicting role descriptions may produce indeterminate boundary classifications
- Overly long string values (exceeding 500 chars) are rejected
- Malformed JSON body returns a 400 error
- Payment failure via x402 results in a 402 response before analysis begins

## How this service works

Choose Blockchain Money Map for human-readable public blockchain reports or x402-paid agent API services.

## Output

A JSON response containing the merchant-of-record boundary analysis: which party holds MoR status given the submitted role-ownership facts, an explanation of how each role (payment, fulfillment, refund, etc.) contributed to the determination, and any policy-driven nuances affecting the classification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "analyze"
   ]
  },
  "facts": {
   "type": "object",
   "required": [
    "platform_role",
    "merchant_role",
    "payment_owner",
    "fulfillment_owner",
    "refund_owner"
   ],
   "properties": {
    "agent_role": {
     "type": "string",
     "maxLength": 500
    },
    "order_owner": {
     "type": "string",
     "maxLength": 500
    },
    "seller_role": {
     "type": "string",
     "maxLength": 500
    },
    "refund_owner": {
     "type": "string",
     "maxLength": 500
    },
    "merchant_role": {
     "type": "string",
     "maxLength": 500
    },
    "payment_owner": {
     "type": "string",
     "maxLength": 500
    },
    "platform_role": {
     "type": "string",
     "maxLength": 500
    },
    "support_owner": {
     "type": "string",
     "maxLength": 500
    },
    "fulfillment_owner": {
     "type": "string",
     "maxLength": 500
    },
    "communication_owner": {
     "type": "string",
     "maxLength": 500
    }
   },
   "additionalProperties": false
  },
  "policy": {
   "type": "object",
   "additionalProperties": true
  },
  "reference_facts": {
   "type": "object",
   "required": [
    "platform_role",
    "merchant_role",
    "payment_owner",
    "fulfillment_owner",
    "refund_owner"
   ],
   "properties": {
    "agent_role": {
     "type": "string",
     "maxLength": 500
    },
    "order_owner": {
     "type": "string",
     "maxLength": 500
    },
    "seller_role": {
     "type": "string",
     "maxLength": 500
    },
    "refund_owner": {
     "type": "string",
     "maxLength": 500
    },
    "merchant_role": {
     "type": "string",
     "maxLength": 500
    },
    "payment_owner": {
     "type": "string",
     "maxLength": 500
    },
    "platform_role": {
     "type": "string",
     "maxLength": 500
    },
    "support_owner": {
     "type": "string",
     "maxLength": 500
    },
    "fulfillment_owner": {
     "type": "string",
     "maxLength": 500
    },
    "communication_owner": {
     "type": "string",
     "maxLength": 500
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockchain-money-map-merchant-of-record-boundary-explainer-769baf7a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockchainmoneymap.com](https://www.zero.xyz/host/api.blockchainmoneymap.com/llms.txt)