commerce_operator_audit
Should you trust this Commerce Payments operator? — Commerce Payments flows are DRIVEN by an operator — it authorizes escrow, captures for merchants and takes the fees. This audits one before you rely on it: 90-day volumes, fees taken, capture-vs-reclaim record (missed capture windows = merchants left unpaid), distinct payers and merchants. verdict: healthy_operator / mixed / sloppy_operator / no_activity. No other tool reads this new Base commerce protocol. Required input: operator. Priced $0.05 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls (no free tier on this tool). No API key required.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"operator": "<operator>"
},
"name": "commerce_operator_audit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| operator | Yes | Operator address |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The result payload. Shape is service-specific; every field is documented in the tool description. | |
| service | No | The service id that answered. | |
| checkedAt | No | ISO-8601 timestamp of when the underlying reads were taken. |