# Document Retrieval — String Normalisation + Numeric Row Ordering

> Document Retrieval — 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-11-04).

Normalises string fields and orders rows numerically for document retrieval records containing retrieved_bytes and request_ms metrics, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-web-09-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/document-retrieval-string-normalisation-numeric-row-ordering-82126876
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GUgZnqCHgrolQiEmaXedR

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 document-retrieval-string-normalisation-numeric-row-ordering-82126876 -d '<json body>'
```

Example prompt: Normalise the site_group strings and sort these document retrieval rows by retrieved_bytes — I have 4 records from October 2026 for group-a and group-b, and I want two analytical reports back.

## When to prefer this

Choose this endpoint when you have tabular document retrieval records (up to 200 rows) and need both string normalisation of categorical fields and numeric ordering of performance metrics (bytes or milliseconds) delivered as two structured reports, all within a single low-cost call. Prefer it over general-purpose data tools when you specifically need the combined string-normalisation-plus-numeric-ordering pipeline for web/document retrieval log data.

## Known failure modes

- More than 200 rows submitted — request rejected or truncated
- Missing required fields (row_id, site_group, date, retrieved_bytes, request_ms) cause validation errors
- Invalid date format (not YYYY-MM-DD) triggers schema rejection
- Null numeric values may affect ordering output
- Invalid field enum value (not retrieved_bytes or request_ms) causes error
- Payment of 0.01 USDC not included — request rejected

## How this service works

Document retrieval — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied document retrieval records (retrieved_bytes, request_ms). 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 covering string-normalised and numerically ordered document retrieval records, ranked by the chosen field (retrieved_bytes or request_ms), for up to 200 input rows. No external lookups or live data are performed; all analysis uses local engines.

## Request schema (JSON Schema)

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

## More

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