# Record Routing Analytics — Numeric Distribution & Base-100 Series

> Record Routing Analytics — Numeric Distribution & Base-100 Series 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 distribution statistics and a base-100 indexed series for accepted_records and rejected_records data across up to 200 rows, producing two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-078?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-analytics-numeric-distribution-base-100-series-f368a1bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nki6wgqV2oOQ_nCBbRZyP

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-analytics-numeric-distribution-base-100-series-f368a1bf -d '<json body>'
```

Example prompt: Can you run the numeric distribution and base-100 series reports on my record routing data? I have 4 rows: row-1 group-a 2026-10-01 accepted=10 rejected=1, row-2 group-b 2026-10-02 accepted=20 rejected=2, row-3 group-a 2026-10-03 accepted=15 rejected=3, row-4 group-b 2026-10-04 accepted=30 rejected=4 — analyze accepted_records starting the index at row 0.

## When to prefer this

Choose this endpoint when you have structured record routing data (accepted/rejected counts by date and group) and need two specific statistical outputs — a numeric distribution and a base-100 indexed series — computed locally without any live lookup, prediction, or external data enrichment. It is best suited for lightweight, cheap ($0.01 USDC) batch analytics on small-to-medium datasets up to 200 rows where the only inputs are row-level accepted and rejected record counts.

## Known failure modes

- Fewer than 1 row supplied — minimum 1 row required
- More than 200 rows submitted — hard limit enforced
- Date field does not match YYYY-MM-DD pattern — schema validation error
- accepted_records or rejected_records values exceed ±1,000,000,000,000 — out-of-range error
- Invalid field enum value (only 'accepted_records' or 'rejected_records' accepted)
- base_index out of range (must be 0–199 and within the number of submitted rows)
- Missing required fields row_id, dataset_group, date, accepted_records, or rejected_records — validation failure
- Payment of 0.01 USDC not included or rejected — 402 Payment Required

## How this service works

Record routing — Numeric distribution + Base-100 series: Numeric distribution + 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 independent analytical reports: (1) a numeric distribution breakdown of the selected field (accepted_records or rejected_records) across the supplied rows, and (2) a base-100 indexed series anchored at the specified base_index row, enabling trend and relative-change analysis. Covers up to 200 rows of input data per call.

## 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-analytics-numeric-distribution-base-100-series-f368a1bf/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)