# Purchase Orders Numeric Row Ordering + Secondary-Measure Weighted Mean

> Purchase Orders Numeric Row Ordering + Secondary-Measure Weighted Mean is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-02).

Ranks purchase order rows by a numeric field and computes a secondary-measure weighted mean, returning two analytical reports for up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-19-121?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/purchase-orders-numeric-row-ordering-secondary-measure-weighted-mean-a7818143
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WjTNo2HscB012x97xbxQt

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 purchase-orders-numeric-row-ordering-secondary-measure-weighted-mean-a7818143 -d '<json body>'
```

Example prompt: I have 4 purchase order rows for our store groups — row-1 group-a 2026-10-01 ordered 10 received 1, row-2 group-b 2026-10-02 ordered 20 received 2, row-3 group-a 2026-10-03 ordered 15 received 3, row-4 group-b 2026-10-04 ordered 30 received 4 — can you rank these rows by ordered_amount and also give me the weighted mean of received_amount weighted by ordered_amount?

## When to prefer this

Choose this endpoint when you need both numeric row ranking and a weighted mean statistic on purchase order data in a single API call for up to 200 rows, and you want a low-cost ($0.01 USDC) batch computation with no external data dependencies. Ideal for retail supply chain analytics pipelines that process PO fulfillment data locally without needing live lookups or predictions.

## Known failure modes

- More than 200 rows submitted — request rejected with validation error
- Missing required fields (row_id, date, ordered_amount, received_amount) — schema validation failure
- Invalid date format not matching YYYY-MM-DD pattern — rejected
- Null values in both numeric fields for all rows — weighted mean undefined
- Invalid field enum value other than 'ordered_amount' or 'received_amount' — rejected

## How this service works

Purchase orders — Numeric row ordering + Secondary-measure weighted mean: Numeric row ordering + Secondary-measure weighted mean for supplied purchase orders records (ordered_amount, received_amount). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.

## Output

Two analytical reports: (1) the input purchase order rows sorted/ranked by the selected numeric field in ascending or descending order, and (2) a weighted mean value of the secondary measure computed using the primary field as weights — both derived from the supplied rows without any external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "store_group",
     "date",
     "ordered_amount",
     "received_amount"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "store_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "ordered_amount": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "received_amount": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "store_group": "group-a",
     "ordered_amount": 10,
     "received_amount": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "store_group": "group-b",
     "ordered_amount": 20,
     "received_amount": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "store_group": "group-a",
     "ordered_amount": 15,
     "received_amount": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "store_group": "group-b",
     "ordered_amount": 30,
     "received_amount": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "ordered_amount",
    "received_amount"
   ],
   "type": "string",
   "default": "ordered_amount"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/purchase-orders-numeric-row-ordering-secondary-measure-weighted-mean-a7818143/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)