# Days Payables Outstanding – Sequential Input-Change Attribution

> Days Payables Outstanding – 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-22).

Calculates how each input change (average payables, credit purchases, period days) incrementally affects Days Payables Outstanding (DPO) by stepping through inputs one at a time in declared order, producing a waterfall attribution report.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-finance-payable-days-waterfall?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/days-payables-outstanding-sequential-input-change-attribution-3f12f1fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IfCtwsJYNCkG5LKKabXyU

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 days-payables-outstanding-sequential-input-change-attribution-3f12f1fd -d '<json body>'
```

Example prompt: Can you run a sequential input-change attribution on my Days Payables Outstanding? Baseline was 365 days, average payables of $4,000, credit purchases of $25,000 — and the new figures are 402 days, average payables $4,400, credit purchases $27,500. Show me how each change contributed to the DPO shift.

## When to prefer this

Choose this endpoint when you need to understand not just the total change in DPO between two periods, but the order-dependent contribution of each individual input. It is ideal for management reporting, financial storytelling, and waterfall charts where attribution sequence matters. Use it over a simple DPO delta calculation when stakeholders need to see which lever (payables balance, credit purchases, or period length) drove the change. Note that results are order-dependent; if you need order-independent (Shapley-style) attribution, a different analysis mode would be more appropriate.

## Known failure modes

- credit_purchases of zero causes division-by-zero; schema enforces exclusiveMinimum:0
- period_days out of range (must be 1–3660) returns validation error
- Missing required fields (average_payables, credit_purchases, period_days) in before or after objects returns error
- Mismatched currency or period units between before and after states produce mathematically valid but economically meaningless results
- Very large values near the 1e12 maximum may introduce floating-point precision issues

## How this service works

Days payables outstanding - Sequential input-change attribution: Change each input from baseline to final in declared field order, reporting each incremental effect; order dependent. Metric: Days payables outstanding. Supplied figures only; returns JSON with formula, units and limitations. One of 50 calculators with 20 analysis modes. No live feed, financial advice or trade execution. 0.01 USDC includes one bounded sequential input-change attribution report.

## Output

A JSON object containing: the DPO formula used, the sequential step-by-step attribution showing each input's incremental effect on DPO as inputs are changed one at a time from baseline to final values in declared field order, units for all figures, and explicit limitations of the sequential (order-dependent) methodology.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object",
   "default": {
    "period_days": 402,
    "average_payables": 4400,
    "credit_purchases": 27500.000000000004
   },
   "required": [
    "average_payables",
    "credit_purchases",
    "period_days"
   ],
   "properties": {
    "period_days": {
     "type": "integer",
     "default": 365,
     "maximum": 3660,
     "minimum": 1
    },
    "average_payables": {
     "type": "number",
     "default": 4000,
     "maximum": 1000000000000,
     "minimum": 0,
     "description": "Amount in a consistent supplied currency and reporting period"
    },
    "credit_purchases": {
     "type": "number",
     "default": 25000,
     "maximum": 1000000000000,
     "minimum": 0,
     "description": "Amount in a consistent supplied currency and reporting period",
     "exclusiveMinimum": 0
    }
   },
   "additionalProperties": false
  },
  "before": {
   "type": "object",
   "default": {
    "period_days": 365,
    "average_payables": 4000,
    "credit_purchases": 25000
   },
   "required": [
    "average_payables",
    "credit_purchases",
    "period_days"
   ],
   "properties": {
    "period_days": {
     "type": "integer",
     "default": 365,
     "maximum": 3660,
     "minimum": 1
    },
    "average_payables": {
     "type": "number",
     "default": 4000,
     "maximum": 1000000000000,
     "minimum": 0,
     "description": "Amount in a consistent supplied currency and reporting period"
    },
    "credit_purchases": {
     "type": "number",
     "default": 25000,
     "maximum": 1000000000000,
     "minimum": 0,
     "description": "Amount in a consistent supplied currency and reporting period",
     "exclusiveMinimum": 0
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/days-payables-outstanding-sequential-input-change-attribution-3f12f1fd/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)
