# MoneyMaker x402 Seller Kit

> MoneyMaker x402 Seller Kit is a paid API for AI agents from moneymaker-x402.monie98-8b9.workers.dev, paid per call via x402, $1/call, status unknown (last checked 2026-09-13).

Returns the x402-seller-kit resource from a paid Base USDC storefront, requiring a $1 USDC micropayment via the x402 protocol before delivering the response.

## Facts

- Endpoint: GET https://moneymaker-x402.monie98-8b9.workers.dev/x402-seller-kit
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/moneymaker-x402-seller-kit-a0d633be
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XWTrYBKDIsfz55ZKyM4JT

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-seller-kit-a0d633be
```

Example prompt: Pay the $1 USDC fee on Base and fetch the MoneyMaker x402 seller kit for me — return the response as JSON.

## When to prefer this

Choose this endpoint when you need to access the specific x402-seller-kit resource on the MoneyMaker storefront and are willing to spend $1 USDC per call via Base. Prefer this over free alternatives when the gated content is specifically what you need and you have a configured x402-compatible wallet and facilitator. This is appropriate for agents that have automated USDC payment authorization built in for the x402 protocol.

## Known failure modes

- 402 Payment Required returned if payment header is missing or malformed — agent must authorize exact USDC amount to payTo via facilitator and retry
- Insufficient USDC balance causes payment authorization to fail before retry
- Wrong network (non-Base) causes payment rejection
- Facilitator unavailable leads to unresolvable 402 loop
- Cloudflare Worker timeout or 5xx if the origin is down
- Invalid format parameter ignored silently by server, no error raised

## 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 payload) representing the seller-kit resource content gated behind the x402 payment wall. The exact fields are open-ended (additionalProperties: true), so the agent should surface the full response body for downstream interpretation.

## 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-seller-kit-a0d633be/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)