# MoneyMaker x402 Worker – /cgw-rem-ops

> MoneyMaker x402 Worker – /cgw-rem-ops is a paid API for AI agents from moneymaker-x402.monie98-8b9.workers.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Paid GET endpoint on the MoneyMaker x402 storefront that returns a response after authorizing $0.10 USDC via the x402 payment protocol on Base.

## Facts

- Endpoint: GET https://moneymaker-x402.monie98-8b9.workers.dev/cgw-rem-ops
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/moneymaker-x402-worker-cgw-rem-ops-a055a581
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7gyzDCWWcW2dChRgEPYtP

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 moneymaker-x402-worker-cgw-rem-ops-a055a581
```

Example prompt: Call the MoneyMaker x402 worker's /cgw-rem-ops route — go ahead and authorize the $0.10 USDC payment on Base via the x402 facilitator if you get a 402, then retry and show me what comes back.

## When to prefer this

Choose this endpoint when you specifically need to interact with the MoneyMaker x402 storefront's /cgw-rem-ops route and you have an x402-capable agent that can handle 402 challenges, authorize Exact USDC payments on Base, and retry. It is not a general-purpose data API — it is best suited for testing x402 payment flows, demonstrating micropayment-gated access, or consuming whatever specific content this route vends.

## Known failure modes

- 402 Payment Required if USDC authorization is not provided or facilitator fails
- Insufficient USDC balance causing payment rejection
- Network timeout on the Cloudflare Worker
- Facilitator unavailable or Base network congestion delaying authorization
- Invalid or expired payment token on retry
- Unknown route behavior if server ignores format hint

## How this service works

Public x402 storefront on Base. Call paid GET routes; on 402 authorize Exact USDC to payTo via facilitator, then retry. Tip jar: GET|POST /tip ($0.10 Exact USDC). Paid email: moneymakerx402@email35.com via Email35 ($0.01) — docs at GET /paid-email.

## Output

An arbitrary JSON object (or raw content) returned by the MoneyMaker Cloudflare Worker after successful x402 USDC payment authorization and retry. The exact schema is open (additionalProperties: true), so content varies by what the worker serves at this route.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "format": {
   "enum": [
    "json",
    "raw"
   ],
   "type": "string",
   "description": "Optional response format hint (ignored by server; present for agent input schema)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/moneymaker-x402-worker-cgw-rem-ops-a055a581/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from moneymaker-x402.monie98-8b9.workers.dev](https://www.zero.xyz/host/moneymaker-x402.monie98-8b9.workers.dev/llms.txt)
