# Launch Your First Paid API — checkout

One product. 5 USDC once, on Base mainnet (eip155:8453). Check current availability at GET /api/checkout?action=offer. Requires an owner-authorized per-purchase budget of at least 5 USDC (some x402 clients default to $1); do not bypass spending limits. No earnings guarantee; requires an existing useful tool/data source, code execution and deployment access. Hosting and operating costs are separate.

One purchase = one completed download; budget for saving the archive on first receipt. The purchased JSON archive contains Markdown instructions, an execution checklist, a starter template, a cost calculator and a worked example. It includes file paths, UTF-8 contents and SHA-256 hashes. There is no free sample.

## Buy it

```
GET https://makemoneyonlineaiagents.xyz/product
```

1. The first request returns **402** with x402 v2 terms in the `PAYMENT-REQUIRED` header and body.
2. Check amount, network, asset and recipient against your authorized spending policy. Some x402 clients cap a single payment at $1 by default; this purchase needs at least 5 USDC authorized.
3. Sign the exact authorization and **retry the same URL** with a `PAYMENT-SIGNATURE` header. Do not send a separate wallet transfer; it will not unlock delivery.
4. On success the body is the archive. Read it fully and verify it against `X-Product-SHA256`.

No account, no pre-registration, and no bearer token are required to buy.

## If delivery is interrupted

The successful response also carries `X-Order-Id`, `X-Recovery-Token` and `X-Recovery-Url`. Save them before reading the body. If the transfer dies, the purchase is not consumed: fetch `X-Recovery-Url` with `Authorization: Bearer <X-Recovery-Token>` to resume it once. After a download completes, that order returns 410.

A replayed payment authorization never settles twice: it returns 409 while the order is unresolved, or 410 once delivered.

If a response is lost after settlement, or a request returns 202, check the order status before taking any other action and contact support with the order ID — never the recovery token or wallet secrets.

## Advanced: pre-created orders

`POST /api/checkout?action=orders` with `Authorization: Bearer <64 lowercase hex characters you generate>` creates an order up front and returns `product_url` and `status_url`. Reuse the same token to recover the order. This path exists for clients that want an order ID before paying; the one-request flow above is the recommended route.

## Terms

Price 5 USDC, charged once, no subscription. Payment must settle before any product content is released.

Access: one purchase includes **one completed download** of version 1.0.0. A transfer interrupted before the full body is received does not consume the purchase and may be retried with the same order ID and token. Once a download completes, the order returns 410 and another copy costs full price. Keep the archive you receive; we cannot restore a lost copy without a new purchase.

Refunds: because the product is delivered immediately, purchases are non-refundable except where delivery failed. If you paid and did not receive a complete archive, email support with the order ID and settlement transaction hash. We review our delivery records for that order and refund in USDC to the paying address when they show delivery did not complete. Do not send another payment while a claim is open.

Licence: you may use and adapt the material and template in your own services. Do not resell or republish the archive itself. Third-party dependencies keep their own licences.

No warranty: the material describes a method for building a paid service. It does not guarantee customers, revenue, or profit, and hosting and operating costs are yours.

Support: support@makemoneyonlineaiagents.xyz.

Privacy: structured checkout events record event type, order ID, environment, HTTP status and duration. Payment records retain the payer, authorization nonce and transaction reference for reconciliation. Application analytics do not record wallet signatures, recovery tokens, IP addresses, raw request bodies or private agent reasoning. Hosting providers may maintain separate access logs.