# Purchase Orders String Normalisation + Two-Measure Correlation

> Purchase Orders String Normalisation + Two-Measure Correlation 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-26).

Normalises string fields and computes two-measure correlation between ordered_amount and received_amount across up to 200 purchase order rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-retail-19-033?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/purchase-orders-string-normalisation-two-measure-correlation-5adf5edc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_17ujpghcbR3i-Ou-GgPHz

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-string-normalisation-two-measure-correlation-5adf5edc -d '<json body>'
```

Example prompt: Can you normalize the string fields in my purchase order records and run a correlation analysis between ordered_amount and received_amount? I have about 50 rows with store groups like 'group-a' and 'group-b' across dates in October 2026 — I want two reports: one on string normalisation and one on how the two amounts correlate.

## When to prefer this

Choose this endpoint when you have up to 200 purchase order rows with ordered_amount and received_amount fields and need both string normalisation and a correlation report in a single low-cost API call. It is purpose-built for retail purchase order analytics and requires no external data or live lookups, making it ideal for offline or batch data-quality and fulfillment-analysis workflows.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, date, ordered_amount, received_amount) cause row rejection
- Date strings not matching YYYY-MM-DD pattern fail schema validation
- Submitting fewer than 1 row returns an error
- Null values in both numeric measures may reduce correlation reliability
- Payment of 0.01 USDC not included causes HTTP 402 response

## How this service works

Purchase orders — String normalisation + Two-measure correlation: String normalisation + Two-measure correlation 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

Returns two independent analytical reports: (1) a string normalisation report that standardises text fields such as store_group across all submitted rows, and (2) a two-measure correlation report quantifying the statistical relationship between ordered_amount and received_amount across the dataset. Both reports are computed locally from the supplied data with no 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/purchase-orders-string-normalisation-two-measure-correlation-5adf5edc/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)