# Payment Reconciliation — String Normalisation + Secondary-Measure Weighted Mean

> Payment Reconciliation — String Normalisation + 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-10-30).

Runs string normalisation and secondary-measure weighted mean analytics on up to 200 payment reconciliation rows (expected vs received amounts), returning two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-08-034?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-reconciliation-string-normalisation-secondary-measure-c10b3883
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EaK9vjMRYW72osQ8g9S-C

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 payment-reconciliation-string-normalisation-secondary-measure-c10b3883 -d '<json body>'
```

Example prompt: Run string normalisation and a secondary-measure weighted mean on these payment reconciliation rows — I have 4 records with instrument groups 'group-a' and 'group-b', dates from 2026-10-01 to 2026-10-04, expected amounts of 10, 20, 15, and 30, received amounts of 1, 2, 3, and 4, and I want the weighted mean calculated on the expected_amount field.

## When to prefer this

Choose this endpoint when you have up to 200 payment reconciliation records and need both string normalisation and a secondary-measure weighted mean computed locally without any external lookups or predictions. It is ideal for finance and accounting workflows that require deterministic, batch analytical reports on expected vs received amounts grouped by instrument. Prefer it over general-purpose analytics tools when you need two specific report types (string normalisation + weighted mean) delivered together at low cost ($0.01 USDC) in a single call.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, instrument_group, date, expected_amount, received_amount) cause schema rejection
- Invalid date format (not YYYY-MM-DD) triggers pattern validation failure
- Amount values outside ±1,000,000,000,000 are rejected
- Empty rows array (minItems:1 not met) returns an error
- Payment failure (insufficient USDC balance) prevents execution

## How this service works

Payment reconciliation — String normalisation + Secondary-measure weighted mean: String normalisation + Secondary-measure weighted mean for supplied payment reconciliation records (expected_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 independent analytical reports: (1) a string normalisation report applied to the payment reconciliation fields, and (2) a secondary-measure weighted mean report computed over the specified numeric field (expected_amount or received_amount), segmented across the supplied rows and instrument groups. No external lookups or predictions are included — all computation is local and deterministic.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "instrument_group",
     "date",
     "expected_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
     },
     "expected_amount": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "received_amount": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "instrument_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "expected_amount": 10,
     "received_amount": 1,
     "instrument_group": "group-a"
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "expected_amount": 20,
     "received_amount": 2,
     "instrument_group": "group-b"
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "expected_amount": 15,
     "received_amount": 3,
     "instrument_group": "group-a"
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "expected_amount": 30,
     "received_amount": 4,
     "instrument_group": "group-b"
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "expected_amount",
    "received_amount"
   ],
   "type": "string",
   "default": "expected_amount"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payment-reconciliation-string-normalisation-secondary-measure-c10b3883/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)