# Schema Conformity — String Normalisation + Numeric Row Ordering

> Schema Conformity — 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-14).

Normalises string fields and orders rows numerically for schema conformity records (valid_records, checked_records), producing two independent analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-02-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/schema-conformity-string-normalisation-numeric-row-ordering-2431a03c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1c2Bbj8y7R95aWwyOIjZU

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 schema-conformity-string-normalisation-numeric-row-ordering-2431a03c -d '<json body>'
```

Example prompt: Can you run string normalisation and numeric row ordering on my schema conformity records? I have up to 50 rows with fields like valid_records and checked_records — I want both reports using valid_records as the target field.

## When to prefer this

Choose this endpoint when you need both string normalisation and numeric row ordering applied together to schema conformity records (up to 200 rows) in a single low-cost call. Ideal when you want two bundled local analytical reports without any live lookups, external API calls, or AI-generated predictions — purely deterministic processing of supplied data.

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Missing required fields (row_id, date, valid_records, checked_records) on any row — validation error
- Date field not matching YYYY-MM-DD pattern — schema validation failure
- Numeric values outside allowed range (-1e12 to 1e12) — rejected
- Empty rows array (minItems: 1 not met) — error response
- Invalid field enum value (must be valid_records or checked_records) — bad request

## How this service works

Schema conformity — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied schema conformity records (valid_records, checked_records). 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 independent analytical reports: (1) a string normalisation report showing how string fields (row_id, dataset_group, date) have been normalised, and (2) a numeric row ordering report showing rows ranked/sorted by the selected numeric field (valid_records or checked_records). No external lookups or live data — purely local analytical processing of the supplied rows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "dataset_group",
     "date",
     "valid_records",
     "checked_records"
    ],
    "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
     },
     "valid_records": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "checked_records": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "dataset_group": "group-a",
     "valid_records": 10,
     "checked_records": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "dataset_group": "group-b",
     "valid_records": 20,
     "checked_records": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "dataset_group": "group-a",
     "valid_records": 15,
     "checked_records": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "dataset_group": "group-b",
     "valid_records": 30,
     "checked_records": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "valid_records",
    "checked_records"
   ],
   "type": "string",
   "default": "valid_records"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/schema-conformity-string-normalisation-numeric-row-ordering-2431a03c/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)