# Commerce Operator Audit (x402 Base Protocol)

> Commerce Operator Audit (x402 Base Protocol) is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Audits a Base Commerce Payments operator's 90-day track record — volumes, fees, capture-vs-reclaim behavior, and payer/merchant diversity — returning a health verdict.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/commerce-operator-audit
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/commerce-operator-audit-x402-base-protocol-65840694
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AofFDBt9QqWR2itSVKql7

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 commerce-operator-audit-x402-base-protocol-65840694
```

Example prompt: Before I use this x402 commerce operator at address 0xAbC123... to handle escrow for my store, can you run a full audit on their 90-day capture record, fees, and merchant payment history and tell me if they're a healthy operator or sloppy?

## When to prefer this

Use this endpoint when you need to evaluate a specific Base Commerce Payments (AuthCaptureEscrow / x402) operator before trusting them with escrow flows. It is the only tool that reads the Base Commerce protocol's two-phase capture data and produces a health verdict. Prefer it over generic wallet analysis tools when the concern is operator reliability for merchant payment capture.

## Known failure modes

- Invalid or malformed operator address returns an error
- Operator address has no on-chain activity — verdict returns no_activity
- Network or RPC issues reading Base chain data may cause timeouts
- Address belongs to a non-operator contract — may return error or empty result

## How this service works

🆕 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.

## Output

Returns a structured report including 90-day payment volumes, fees taken by the operator, capture-vs-reclaim ratio (missed captures indicate merchants left unpaid), count of distinct payers and merchants, and a summary verdict: healthy_operator, mixed, sloppy_operator, or no_activity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "operator"
     ],
     "properties": {
      "operator": {
       "type": "string",
       "description": "Operator address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/commerce-operator-audit-x402-base-protocol-65840694/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)