# Record Routing — Record Quality Audit + Date by Category Pivot

> Record Routing — Record Quality Audit + Date by Category Pivot 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-24).

Runs two analytical reports on record routing data: a quality audit of accepted/rejected records and a date-by-category pivot, for up to 200 rows of supplied data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-017?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-record-quality-audit-date-by-category-pivot-4038165d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AmERXS_CzYt4rleRSZt4T

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-record-quality-audit-date-by-category-pivot-4038165d -d '<json body>'
```

Example prompt: Can you run a record quality audit and a date-by-category pivot on this record routing data? I have 4 rows: row-1 on 2026-10-01 in group-a with 10 accepted and 1 rejected, row-2 on 2026-10-02 in group-b with 20 accepted and 2 rejected, row-3 on 2026-10-03 in group-a with 15 accepted and 3 rejected, and row-4 on 2026-10-04 in group-b with 30 accepted and 4 rejected — analyze the accepted_records field.

## When to prefer this

Choose this endpoint when you have up to 200 rows of record routing data with accepted/rejected record counts and need both a quality audit and a date-by-category pivot in a single call. It is ideal for data pipeline monitoring, batch quality reviews, and category-level breakdowns without requiring any external data sources or live lookups. Prefer this over generic analytics tools when the data is already structured with row_id, dataset_group, and date fields and you need two specific pre-built report types in one low-cost API call.

## Known failure modes

- Fewer than 1 row or more than 200 rows supplied — validation error
- Row missing required fields (row_id, dataset_group, date, accepted_records, rejected_records) — schema validation failure
- Date field not matching YYYY-MM-DD format — pattern validation error
- Field selector not one of 'accepted_records' or 'rejected_records' — enum validation error
- Numeric values outside allowed range (±1,000,000,000,000) — validation failure
- Payment of 0.01 USDC not completed — 402 Payment Required

## How this service works

Record routing — Record quality audit + Date by category pivot: Record quality audit + Date by category pivot 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 record quality audit summarizing accepted and rejected record distributions and quality metrics across the supplied rows, and (2) a date-by-category pivot table breaking down the selected field (accepted_records or rejected_records) by date and dataset group — all 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-record-quality-audit-date-by-category-pivot-4038165d/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)