# Aether Invoice Triage – Base Onchain Data & Token Risk

> Aether Invoice Triage – Base Onchain Data & Token Risk is a paid API for AI agents from aether-x402.vercel.app, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-12).

Triages an invoice by amount, aging, and reference to return a next-action recommendation and aging category, payable via x402 (USDC on Base).

## Facts

- Endpoint: POST https://aether-x402.vercel.app/v1/invoice/triage?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aether-invoice-triage-base-onchain-data-token-risk-77867e7c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_L4pmeKQh47_97SHCaovc8

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 aether-invoice-triage-base-onchain-data-token-risk-77867e7c -d '<json body>'
```

Example prompt: Can you triage invoice INV-4821 for client ref CL-990, which is for $2,500 and is 45 days overdue, and tell me what the recommended next action is and its aging category?

## When to prefer this

Choose this endpoint when you need an automated, pay-per-call invoice triage decision (next action + aging category) integrated into an agentic accounts-receivable or collections workflow that pays via x402 USDC on Base. Prefer it over generic invoice tools when you need blockchain-native micropayment access and Base onchain auditability.

## Known failure modes

- Missing required fields (invoiceNumber or amount) returns a validation error
- Payment not included or insufficient USDC via x402 returns a 402 Payment Required response
- Amount exceeding 100,000,000 or daysOverdue outside -365 to 3650 range returns schema validation error
- Invalid clientReference format or length returns a 400 error

## How this service works

Pay-per-call Base onchain data, token risk verdicts and x402 payability audits over x402 (USDC on Base).

## Output

Returns a JSON object with a 'nextAction' field (e.g. 'prepare_reminder') indicating the recommended action to take on the invoice, and an 'agingCategory' field (e.g. 'pending') classifying the invoice's overdue status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "amount": {
   "type": "number",
   "maximum": 100000000,
   "minimum": 0
  },
  "daysOverdue": {
   "type": "integer",
   "maximum": 3650,
   "minimum": -365
  },
  "invoiceNumber": {
   "type": "string",
   "maxLength": 100,
   "minLength": 1
  },
  "clientReference": {
   "type": "string",
   "maxLength": 100,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "nextAction": "prepare_reminder",
  "agingCategory": "pending"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aether-invoice-triage-base-onchain-data-token-risk-77867e7c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aether-x402.vercel.app](https://www.zero.xyz/host/aether-x402.vercel.app/llms.txt)