# Settlement Timing — String Normalisation + Adjacent Row Changes

> Settlement Timing — String Normalisation + Adjacent Row Changes 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 adjacent-row change detection on settlement timing records (settlement_minutes, payment_count) for up to 200 rows, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-18-029?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/settlement-timing-string-normalisation-adjacent-row-changes-4a672875
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6YvbEa1c9ZXTUGTRGzdgz

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 settlement-timing-string-normalisation-adjacent-row-changes-4a672875 -d '<json body>'
```

Example prompt: Can you run string normalisation and adjacent-row change detection on these settlement timing records? I have 4 rows with columns row_id, instrument_group, date, settlement_minutes, and payment_count — analyse the settlement_minutes field across rows row-1 through row-4 covering 2026-10-01 to 2026-10-04.

## When to prefer this

Choose this endpoint when you have tabular settlement timing data and need two specific local analytical operations — string normalisation and adjacent-row change detection — applied in a single call without any external data lookup or live market data. Ideal for data cleaning pipelines, sequential audit workflows, or QA checks on financial settlement records where you want both string hygiene and row-over-row delta detection at a low per-call cost.

## Known failure modes

- More than 200 rows submitted — request exceeds maxItems limit
- Missing required fields (row_id, instrument_group, date, settlement_minutes, payment_count) causes validation error
- Invalid date format (not YYYY-MM-DD) rejected by pattern constraint
- Numeric fields outside allowed range (-1000000000000 to 1000000000000) rejected
- Invalid field enum value (must be 'settlement_minutes' or 'payment_count')
- Empty rows array (minItems: 1) causes rejection

## How this service works

Settlement timing — String normalisation + Adjacent row changes: String normalisation + Adjacent row changes for supplied settlement timing records (settlement_minutes, payment_count). 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) string normalisation results for the selected field across all supplied rows, standardising instrument_group and other string values; (2) adjacent row change detection showing value differences between consecutive rows for the chosen numeric field (settlement_minutes or payment_count). Covers up to 200 input rows with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/settlement-timing-string-normalisation-adjacent-row-changes-4a672875/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)