# three.ws Print Order API

> three.ws Print Order API is a paid API for AI agents from three.ws, paid per call via x402, $12/call, status unknown (last checked 2026-10-11).

Submits a print order for a 3D-agent-related product (e.g. physical merchandise or avatar output) via a paid HTTP POST, charged at $12 USDC per call using the x402 micropayment protocol.

## Facts

- Endpoint: POST https://three.ws/api/x402/print-order?utm_source=zero.xyz
- Price: $12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/three-ws-print-order-api-f2722649
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xxr2Lk4NXy-1SspZf2fmC

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 three-ws-print-order-api-f2722649 -d '<json body>'
```

Example prompt: Place a print order on three.ws for my 3D AI agent avatar — submit the order details as a POST request and authorize the $12 USDC payment.

## When to prefer this

Use this endpoint when you need to programmatically submit a print order for a three.ws 3D AI agent product and can authorize a $12 USDC micropayment via the x402 protocol. Prefer this over manual ordering when integrating print fulfillment into an automated agent workflow or e-commerce pipeline.

## Known failure modes

- Insufficient USDC balance or failed x402 payment authorization — payment declined
- Missing required fields in the request body — 400 validation error
- Invalid HTTP method (only POST/PUT/PATCH accepted) — method not allowed
- Network timeout or server error during order processing — 5xx response
- Malformed JSON body — parsing error

## How this service works

Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.

## Output

Returns a print order confirmation object, likely including an order ID, status, and any relevant fulfillment details. The exact response schema is not fully documented but follows the x402 paid-endpoint pattern with a JSON body response.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    }
   },
   "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/three-ws-print-order-api-f2722649/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from three.ws](https://www.zero.xyz/host/three.ws/llms.txt)