# Transformation Throughput — String Normalisation + Keyed Dataset Comparison

> Transformation Throughput — String Normalisation + Keyed Dataset Comparison 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-15).

Analyzes transformation throughput records (processed_rows, duration_seconds) by performing string normalization and keyed dataset comparison across two supplied datasets, returning 2 analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-13-036?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transformation-throughput-string-normalisation-keyed-dataset-comparison-2c579b6d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LhVRxSAxCDBQVnnjwbPqL

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 transformation-throughput-string-normalisation-keyed-dataset-comparison-2c579b6d -d '<json body>'
```

Example prompt: Can you compare these two batches of ETL transformation records — each up to 200 rows with processed_rows and duration_seconds fields — using string normalization and keyed dataset comparison to find where they differ?

## When to prefer this

Choose this endpoint when you need to compare two batches of transformation throughput records (up to 200 rows each) using both string normalization and keyed matching logic, and want two distinct analytical reports from a single cheap call. Prefer it over general-purpose data comparison tools when your data specifically involves processed_rows and duration_seconds metrics keyed by row_id and dataset_group.

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Missing required fields (row_id, dataset_group, date, processed_rows, duration_seconds) cause validation errors
- Invalid date format (must match YYYY-MM-DD pattern) triggers schema rejection
- Numeric values outside allowed range cause field-level errors
- Empty rows array (minItems: 1 not met) returns error
- Payment of 0.01 USDC not confirmed — endpoint returns 402

## How this service works

Transformation throughput — String normalisation + Keyed dataset comparison: String normalisation + Keyed dataset comparison for supplied transformation throughput records (processed_rows, duration_seconds). 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 string normalization report applied to the supplied transformation throughput records, and (2) a keyed dataset comparison report highlighting differences between the two supplied row arrays, both computed locally without external lookups or predictions.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transformation-throughput-string-normalisation-keyed-dataset-comparison-2c579b6d/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)