# MoneyMaker x402 Worker – Three.js Pack

> MoneyMaker x402 Worker – Three.js Pack is a paid API for AI agents from moneymaker-x402.monie98-8b9.workers.dev, paid per call via x402, $12/call, status unknown (last checked 2026-09-14).

Returns a Three.js asset pack (resources, code snippets, or data) via a paid x402 GET endpoint on Base, requiring USDC payment before content is delivered.

## Facts

- Endpoint: GET https://moneymaker-x402.monie98-8b9.workers.dev/threejs-pack
- Price: $12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/moneymaker-x402-worker-three-js-pack-8f379eb4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ghz7L5aDLOROSVlLJybUP

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-three-js-pack-8f379eb4
```

Example prompt: Fetch me the Three.js pack from MoneyMaker's x402 storefront — go ahead and authorize the $12 USDC payment on Base to unlock and download the contents.

## When to prefer this

Use this endpoint when you need Three.js assets or resources delivered via a Web3 x402 micropayment flow on Base, and your agent stack supports USDC authorization through an x402-compatible facilitator. Prefer this over traditional CDN or npm asset sources when operating in a crypto-native or agent-economy context where on-chain payment provenance matters.

## Known failure modes

- HTTP 402 returned if payment is not yet authorized — agent must authorize exact USDC amount to payTo address via facilitator then retry
- Payment amount mismatch causes authorization rejection
- Invalid or expired payment header leads to 402 loop
- Network errors on Cloudflare Worker edge
- Base blockchain congestion causing slow payment confirmation
- Malformed format parameter ignored silently but may cause unexpected output shape

## 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 object (JSON or raw) containing the Three.js pack payload — likely asset references, code snippets, configuration files, or bundle data — returned after successful x402 USDC payment authorization on Base.

## 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-three-js-pack-8f379eb4/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)