# Record Routing Numeric Row Ordering and Base-100 Series Analytics

> Record Routing Numeric Row Ordering and Base-100 Series Analytics 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).

Computes numeric row ordering and base-100 index series for accepted_records and rejected_records fields across up to 200 rows of record routing data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-117?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/record-routing-numeric-row-ordering-and-base-100-series-analytics-fdeaafe8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tfhiA6oZSTJImCERMielx

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 record-routing-numeric-row-ordering-and-base-100-series-analytics-fdeaafe8 -d '<json body>'
```

Example prompt: I have 4 rows of record routing data for groups 'group-a' and 'group-b' from October 2026 — can you rank them by accepted_records and give me both a numeric row ordering and a base-100 index series starting at base index 0?

## When to prefer this

Choose this endpoint when you have tabular record routing data (up to 200 rows) with accepted and rejected record counts and need both a numeric row ranking and a base-100 index series computed from your own supplied data — no external data fetching, no ML predictions, just deterministic analytical computation on data you provide. Ideal for ETL monitoring dashboards, data quality reporting, and pipeline performance comparisons where you want normalized index scores alongside raw rank ordering.

## Known failure modes

- More than 200 rows submitted — request will fail or be truncated at max item limit
- Missing required fields (row_id, date, dataset_group, accepted_records, rejected_records) cause validation errors
- Invalid date format (not YYYY-MM-DD) triggers schema validation failure
- base_index value out of range 0–199 causes an error
- All null values in the selected field may produce undefined ranking or indexing output
- Payment of 0.01 USDC not completed — request rejected by x402 payment layer

## How this service works

Record routing — Numeric row ordering + Base-100 series: Numeric row ordering + Base-100 series for supplied record routing records (accepted_records, rejected_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

Returns two analytical reports: (1) a numeric row ordering ranking each submitted row by the selected field (accepted_records or rejected_records), and (2) a base-100 index series normalizing the field values relative to a configurable base index row. 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",
     "accepted_records",
     "rejected_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
     },
     "accepted_records": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "rejected_records": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "dataset_group": "group-a",
     "accepted_records": 10,
     "rejected_records": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "dataset_group": "group-b",
     "accepted_records": 20,
     "rejected_records": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "dataset_group": "group-a",
     "accepted_records": 15,
     "rejected_records": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "dataset_group": "group-b",
     "accepted_records": 30,
     "rejected_records": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "accepted_records",
    "rejected_records"
   ],
   "type": "string",
   "default": "accepted_records"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-numeric-row-ordering-and-base-100-series-analytics-fdeaafe8/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)