# lab.paidapis.net Invoice Create

> lab.paidapis.net Invoice Create is a paid API for AI agents from lab.paidapis.net, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Issues a signed, deferred-payment invoice to a specified wallet address for a given USDC amount, to be settled later at a dynamic /pay sub-resource.

## Facts

- Endpoint: POST https://lab.paidapis.net/api/invoice/create
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lab-paidapis-net-invoice-create-15ae6b25
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_I4ULQvCnM-yEaRtKk0H7w

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 lab-paidapis-net-invoice-create-15ae6b25 -d '<json body>'
```

Example prompt: Create a signed USDC invoice for wallet address 0xABC123...DEF for 25 USDC, due in 14 days, with a memo saying 'API usage — March 2025' and line items for compute (20 USDC) and storage (5 USDC).

## When to prefer this

Choose this endpoint when you need to issue a deferred, asynchronous payment request rather than collecting payment synchronously. It is ideal for agent-to-agent billing, freelance crypto invoicing, or any workflow where the payer needs to settle at a later time via a separate /pay sub-resource. Prefer this over synchronous payment endpoints when payment timing is flexible or must be negotiated separately.

## Known failure modes

- Invalid or malformed payerAddress returns a validation error
- amountUsdc of zero or negative value rejected
- Malformed dueBy ISO 8601 string causes a parsing error
- lineItems containing invalid JSON structure returns a schema error
- Duplicate invoice creation for same payer/amount/memo may produce a new invoice each time (non-idempotent)
- Missing required fields (payerAddress, amountUsdc) results in a 400 error

## How this service works

Machine-to-machine invoicing: issue a signed invoice now (payerAddress, amountUsdc, optional lineItems/memo/dueBy); the payer settles it later at its own dynamically-priced /pay sub-resource, instead of paying synchronously like every other endpoint here.

## Output

Returns a signed invoice object including a unique invoice ID, the payer wallet address, total USDC amount due, optional line items and memo, the due date, and a /pay sub-resource URL the payer can later call to settle the invoice at dynamically determined pricing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "memo": {
   "type": "string",
   "description": "Free-text note."
  },
  "dueBy": {
   "type": "string",
   "description": "ISO 8601 due date (default 7 days out)."
  },
  "lineItems": {
   "type": "string",
   "description": "JSON array of {\"description\",\"amountUsdc\"} objects, for record-keeping."
  },
  "amountUsdc": {
   "type": "number",
   "description": "Total amount due, in USDC."
  },
  "payerAddress": {
   "type": "string",
   "description": "Wallet address expected to pay this invoice."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lab-paidapis-net-invoice-create-15ae6b25/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lab.paidapis.net](https://www.zero.xyz/host/lab.paidapis.net/llms.txt)