# Unit Return Rate Sequential Input-Change Attribution

> Unit Return Rate Sequential Input-Change Attribution is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-27).

Performs sequential (waterfall) attribution analysis to decompose how changes in sold units and returned units drive a change in the unit return rate between two periods.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-retail-unit-return-waterfall?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/unit-return-rate-sequential-input-change-attribution-cf1f3093
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lk3GiN0i2pINHmtt_I7W8

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 unit-return-rate-sequential-input-change-attribution-cf1f3093 -d '<json body>'
```

Example prompt: We went from 100 sold units and 5 returns last month to 110 sold units and 5.5 returns this month — can you do a sequential waterfall attribution to show how much of the return rate change came from the change in sold units versus the change in returned units?

## When to prefer this

Use this endpoint when you need to isolate and quantify how much each individual input variable (sold units vs returned units) contributed to a change in the unit return rate between two time periods, using a sequential waterfall methodology. Prefer this over simple delta calculations when stakeholders need to understand cause-attribution rather than just the net change. It is specifically suited for retail scenarios where only aggregated sold and returned unit counts are available.

## Known failure modes

- sold_units equal to zero causes division-by-zero in return rate calculation — likely returns an error or undefined result
- extremely large unit values near the 1 trillion maximum may cause precision issues
- missing required fields (sold_units or returned_units) will cause schema validation failure
- returned_units exceeding sold_units produces a return rate over 100%, which is mathematically valid but may be flagged

## How this service works

Unit return rate - Sequential input-change attribution: Sequential input-change attribution for Unit return rate. Supplied retail figures only. Local calculation and scenario analysis; no live inventory, account access, platform fee lookup or order execution. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded sequential input-change attribution deliverable.

## Output

Returns a sequential (waterfall) attribution breakdown showing the before and after unit return rates, the total change in return rate, and the individual contribution of each input change (sold units delta and returned units delta) in the order they are applied sequentially, so users can understand which factor drove how much of the movement.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object",
   "default": {
    "sold_units": 110.00000000000001,
    "returned_units": 5.5
   },
   "required": [
    "returned_units",
    "sold_units"
   ],
   "properties": {
    "sold_units": {
     "type": "number",
     "default": 100,
     "maximum": 1000000000000,
     "minimum": 0,
     "exclusiveMinimum": 0
    },
    "returned_units": {
     "type": "number",
     "default": 5,
     "maximum": 1000000000000,
     "minimum": 0
    }
   },
   "additionalProperties": false
  },
  "before": {
   "type": "object",
   "default": {
    "sold_units": 100,
    "returned_units": 5
   },
   "required": [
    "returned_units",
    "sold_units"
   ],
   "properties": {
    "sold_units": {
     "type": "number",
     "default": 100,
     "maximum": 1000000000000,
     "minimum": 0,
     "exclusiveMinimum": 0
    },
    "returned_units": {
     "type": "number",
     "default": 5,
     "maximum": 1000000000000,
     "minimum": 0
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/unit-return-rate-sequential-input-change-attribution-cf1f3093/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)