# Agent Print — 3D Print On Demand

> Agent Print — 3D Print On Demand is a paid API for AI agents from api.agentprint.art, paid per call via x402, $5/call, status unknown (last checked 2026-10-11).

Places an on-demand 3D print order, paying per-print via card or USDC on Base/Solana

## Facts

- Endpoint: POST https://api.agentprint.art/print/order?utm_source=zero.xyz
- Price: $5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-print-3d-print-on-demand-8e344101
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T-l5-cS6tyQ1xKOJADaHK

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 agent-print-3d-print-on-demand-8e344101 -d '<json body>'
```

Example prompt: Place a 3D print order for my model through Agent Print and pay with USDC — here are the print properties I need for a small custom figurine.

## When to prefer this

Choose this endpoint when an AI agent needs to autonomously place a physical 3D print order as part of an automated workflow, especially when paying programmatically with USDC on Base or Solana. It is best suited for per-print, pay-as-you-go manufacturing without requiring a subscription or manual fulfillment steps. Prefer this over traditional print services when the workflow is agent-driven and crypto payment rails are acceptable or preferred.

## Known failure modes

- Insufficient USDC balance or card payment failure — order rejected with payment error
- Invalid or missing model properties — request rejected with schema validation error
- Unsupported print specification — service may return an error indicating incompatible parameters
- Network or service downtime — order may fail to submit with a 5xx error
- Model file too complex or outside printable bounds — order rejected during processing

## How this service works

On-demand 3D printing for agents. Pay per print with card or USDC on Base/Solana.

## Output

Returns a JSON object with a status field (e.g. 'processing') and an order ID (e.g. 'SLANT_1234567890') confirming the print job has been submitted and is queued for production.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "processing",
  "orderId": "SLANT_1234567890"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-print-3d-print-on-demand-8e344101/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentprint.art](https://www.zero.xyz/host/api.agentprint.art/llms.txt)