# Invoice Ageing — String Normalisation + Numeric Row Ordering

> Invoice Ageing — String Normalisation + Numeric Row Ordering 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-25).

Normalises string fields and orders rows numerically for invoice ageing records containing outstanding_amount and age_days, producing 2 analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-07-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoice-ageing-string-normalisation-numeric-row-ordering-ca7651c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hw-ESJ_A0iYvDqGkHRE0n

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 invoice-ageing-string-normalisation-numeric-row-ordering-ca7651c9 -d '<json body>'
```

Example prompt: Can you normalise the string fields and sort these invoice ageing rows numerically by outstanding_amount? I have 4 invoices: row-1 on 2026-10-01 in group-a for $10 aged 1 day, row-2 on 2026-10-02 in group-b for $20 aged 2 days, row-3 on 2026-10-03 in group-a for $15 aged 3 days, and row-4 on 2026-10-04 in group-b for $30 aged 4 days — I need 2 reports back.

## When to prefer this

Choose this endpoint when you need lightweight, local string cleaning and numeric ordering on invoice ageing data (up to 200 rows) without any external lookup, prediction, or live data enrichment. It is particularly suitable when you want two distinct reports — normalisation and ordering — in a single low-cost call ($0.01 USDC) and have no need for forecasting, credit scoring, or third-party data.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, date, outstanding_amount, age_days) causes a schema rejection
- Invalid date format (not YYYY-MM-DD) triggers a pattern validation failure
- Null values in numeric fields may affect ordering output
- Submitting 0 rows or an empty array is rejected by minItems constraint

## How this service works

Invoice ageing — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied invoice ageing records (outstanding_amount, age_days). 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 covering the supplied invoice ageing rows: one applying string normalisation to text fields (e.g. instrument_group) and one ordering rows numerically by the selected field (outstanding_amount or age_days). No external data is fetched; all processing is performed locally on the submitted rows.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoice-ageing-string-normalisation-numeric-row-ordering-ca7651c9/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)