# ManyLives Return Triage

> ManyLives Return Triage is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-18).

Analyzes a customer return request against a store's return policy and applicable consumer law to determine the correct remedy outcome

## Facts

- Endpoint: POST https://api.manylives.me/paid/text/return-triage?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-return-triage-0a38b6e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PrG2JfxK1ZF8MqvAao1xd

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 manylives-return-triage-0a38b6e7 -d '<json body>'
```

Example prompt: A customer says 'it stopped working after two days' about headphones they bought for $129, delivered on August 1st 2026, and they're requesting a return today October 14th 2026. Our policy allows 30-day returns with a 10% restocking fee and no change-of-mind on clearance items — can you triage this return and tell me what remedy we're obligated to offer?

## When to prefer this

Choose this endpoint when you need automated, legally-aware triage of customer return requests that goes beyond simple date-window checks — particularly when Australian Consumer Law (ACCC) or equivalent consumer guarantees may override a store's stated policy. It is especially valuable when product faults are alleged, since the outcome must account for statutory remedies regardless of policy terms. Prefer this over a simple rules engine when you need a natural-language rationale suitable for customer-facing communication.

## Known failure modes

- Missing required 'request' field returns an error — all sub-fields like text, delivered_date, request_date, and price should be included
- Invalid date format (not YYYY-MM-DD) may cause parsing failures
- Unsupported country codes may fall back to AU defaults or return an error
- Ambiguous or very short customer request text may produce low-confidence or generic outcomes
- Malformed policy JSON may cause the policy to be ignored or an error returned

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

A JSON object containing: an outcome field ('remedy', 'decline', or similar), a fault boolean indicating whether the product is considered faulty, a reason string classifying the return type (e.g. 'faulty', 'change_of_mind'), a why field with plain-language legal rationale citing applicable consumer guarantee rules, a checks array with per-rule pass/fail results and detail text, and a flags array for any special conditions or alerts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "policy": {
   "type": "string",
   "examples": [
    {
     "window_days": 30,
     "change_of_mind": true,
     "restocking_fee_pct": 10,
     "final_sale_categories": [
      "clearance"
     ]
    }
   ],
   "description": "{window_days, final_sale_categories, condition_required, change_of_mind (true/false), restocking_fee_pct, review_over}"
  },
  "country": {
   "type": "string",
   "description": "optional, default AU"
  },
  "request": {
   "type": "string",
   "examples": [
    {
     "text": "It stopped working after two days",
     "price": 129,
     "category": "headphones",
     "request_date": "2026-10-14",
     "delivered_date": "2026-08-01"
    }
   ],
   "description": "{text (the customer's words; no names or contact details needed), delivered_date, request_date (YYYY-MM-DD), category, price, condition, tracking_status, returns_last_90_days}"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "why": "faulty, damaged, wrong or not-as-described goods are covered by the consumer guarantees whatever the store's policy or window says; for a major failure the customer chooses refund, repair or replacement (ACCC).",
  "fault": true,
  "flags": [],
  "checks": [
   {
    "ok": false,
    "check": "return window",
    "detail": "74 days after delivery; the policy allows 30."
   }
  ],
  "reason": "faulty",
  "outcome": "remedy"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-return-triage-0a38b6e7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)