# Data Catalog Coverage — String Normalisation + Numeric Row Ordering

> Data Catalog Coverage — 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-23).

Normalises dataset_group strings and orders rows numerically by documented_fields or total_fields for up to 200 data catalog coverage records, returning two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-21-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-catalog-coverage-string-normalisation-numeric-row-ordering-b62a5fe6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uTN7ZBTUR3GrGy4xsYAQW

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-catalog-coverage-string-normalisation-numeric-row-ordering-b62a5fe6 -d '<json body>'
```

Example prompt: Can you normalize the dataset group strings and order these catalog coverage rows numerically by documented_fields? I have 4 rows: row-1 for group-a on 2026-10-01 with 10 documented and 1 total field, row-2 for group-b on 2026-10-02 with 20 documented and 2 total fields, row-3 for group-a on 2026-10-03 with 15 documented and 3 total fields, and row-4 for group-b on 2026-10-04 with 30 documented and 4 total fields.

## When to prefer this

Choose this endpoint when you need lightweight, fast, offline-style analytics on data catalog coverage records specifically — combining string normalisation of group labels with numeric ordering of documented or total field counts in a single paid call. Ideal for data governance pipelines, catalog audits, or preprocessing steps where no external lookup, prediction, or live data fetch is needed and the dataset fits within 200 rows.

## Known failure modes

- More than 200 rows submitted — request rejected due to maxItems constraint
- Missing required fields (row_id, dataset_group, date, documented_fields, total_fields) — validation error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Numeric field values outside allowed range (-1e12 to 1e12) — validation error
- Empty rows array — minItems constraint violation
- Payment not received or insufficient USDC — x402 payment required error

## How this service works

Data catalog coverage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied data catalog coverage records (documented_fields, total_fields). 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 independent analytical reports: (1) a string normalisation report for the dataset_group field across all supplied rows, and (2) a numeric row ordering report ranking rows by the selected numeric field (documented_fields or total_fields). Both reports are generated locally with no external lookups, covering up to 200 input rows.

## Request schema (JSON Schema)

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

## More

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