# Data Ingestion Batches — Numeric Row Ordering + Two-Measure Correlation

> Data Ingestion Batches — 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-16).

Analyzes up to 200 data ingestion batch records by ranking rows numerically and computing correlation between received_rows and accepted_rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-01-120?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-ingestion-batches-numeric-row-ordering-two-measure-correlation-7b2c5886
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_odPX5JKL7hsWZvAYFPxuU

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 data-ingestion-batches-numeric-row-ordering-two-measure-correlation-7b2c5886 -d '<json body>'
```

Example prompt: I have up to 200 rows of data ingestion batch records with received_rows and accepted_rows — can you rank them numerically by received_rows and also compute the correlation between received_rows and accepted_rows across all the batches?

## When to prefer this

Choose this endpoint when you have up to 200 data ingestion batch records and need both a numeric ranking of rows and a correlation between received_rows and accepted_rows in a single low-cost call. It is ideal for ETL monitoring, pipeline quality checks, and batch acceptance analysis where you supply your own data and need two analytical outputs simultaneously without any external data fetching or prediction.

## Known failure modes

- Fewer than 1 row submitted — minimum 1 row required
- More than 200 rows submitted — maximum batch size exceeded
- Missing required fields (row_id, dataset_group, date, received_rows, accepted_rows) on any row
- Date field not matching YYYY-MM-DD format
- Numeric values outside allowed range (-1,000,000,000,000 to 1,000,000,000,000)
- All accepted_rows or received_rows values are null — correlation cannot be computed
- Invalid field enum value provided (must be 'received_rows' or 'accepted_rows')

## How this service works

Data ingestion batches — Numeric row ordering + Two-measure correlation: Numeric row ordering + Two-measure correlation for supplied data ingestion batches records (received_rows, accepted_rows). 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 ordering of the submitted rows ranked by the selected field (received_rows or accepted_rows), and (2) a correlation analysis between received_rows and accepted_rows across all supplied records. 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",
     "dataset_group",
     "date",
     "received_rows",
     "accepted_rows"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "accepted_rows": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "dataset_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "received_rows": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "accepted_rows": 1,
     "dataset_group": "group-a",
     "received_rows": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "accepted_rows": 2,
     "dataset_group": "group-b",
     "received_rows": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "accepted_rows": 3,
     "dataset_group": "group-a",
     "received_rows": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "accepted_rows": 4,
     "dataset_group": "group-b",
     "received_rows": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "received_rows",
    "accepted_rows"
   ],
   "type": "string",
   "default": "received_rows"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-ingestion-batches-numeric-row-ordering-two-measure-correlation-7b2c5886/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)