# Settlement Timing — Numeric Row Ordering + Two-Measure Correlation

> Settlement Timing — Numeric Row Ordering + 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).

Computes numeric row ordering and two-measure correlation analysis for settlement timing records (settlement_minutes, payment_count) using local analytical engines, returning two reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-18-120?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/settlement-timing-numeric-row-ordering-two-measure-correlation-3cca1229
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uVXhK_0mg_eNuG5-4ZHI6

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-numeric-row-ordering-two-measure-correlation-3cca1229 -d '<json body>'
```

Example prompt: Can you run a numeric row ordering and two-measure correlation analysis on my settlement timing data? I have rows with settlement_minutes and payment_count for instrument groups over the past week — analyze the settlement_minutes field and give me both reports.

## When to prefer this

Choose this endpoint when you need both a ranked ordering of settlement timing rows and a correlation between settlement_minutes and payment_count in a single low-cost call. It is ideal for offline/batch financial analytics on pre-collected settlement data (up to 200 rows) where no live data fetch, prediction, or external enrichment is needed. At $0.01 USDC for two reports, it is cost-effective for routine settlement audits and performance reviews.

## Known failure modes

- More than 200 rows submitted — request will be rejected or truncated
- Missing required fields (row_id, instrument_group, date, settlement_minutes, payment_count) cause validation errors
- Invalid date format (must match YYYY-MM-DD pattern) causes schema rejection
- All null values in the target measure prevent meaningful ordering or correlation
- Payment failure or insufficient USDC balance blocks execution

## How this service works

Settlement timing — Numeric row ordering + Two-measure correlation: Numeric row ordering + Two-measure correlation 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

Returns two analytical reports: (1) a numeric row ordering report ranking the supplied rows by the selected field (settlement_minutes or payment_count), and (2) a two-measure correlation report showing the statistical relationship between settlement_minutes and payment_count across the supplied dataset. Both reports are computed locally 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-numeric-row-ordering-two-measure-correlation-3cca1229/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)