# Record Routing Analytics: Two-Measure Correlation + Date-by-Category Pivot

> Record Routing Analytics: Two-Measure Correlation + 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-23).

Computes a two-measure correlation (accepted vs rejected records) and a date-by-category pivot table for up to 200 supplied record routing rows in a single paid call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-182?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-two-measure-correlation-date-by-category-pivot-5b94e1a5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XLmsf0R9OZOAkajVP3k3r

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-two-measure-correlation-date-by-category-pivot-5b94e1a5 -d '<json body>'
```

Example prompt: Run a two-measure correlation between accepted_records and rejected_records plus a date-by-category pivot on this record routing data: group-a had 10 accepted and 1 rejected on 2026-10-01, group-b had 20 accepted and 2 rejected on 2026-10-02, group-a had 15 accepted and 3 rejected on 2026-10-03, and group-b had 30 accepted and 4 rejected on 2026-10-04.

## When to prefer this

Choose this endpoint when you need both a two-measure correlation and a date-by-category pivot on record routing data (accepted/rejected counts) in a single low-cost call ($0.01 USDC). It is ideal for offline batch analytics on up to 200 rows of supplied data where no live lookup, prediction, or external enrichment is needed. Prefer alternatives if you need more than 200 rows, a single report type, or metrics beyond accepted/rejected record counts.

## Known failure modes

- Fewer than 1 row submitted — validation error
- More than 200 rows submitted — request rejected
- Row missing required fields (row_id, date, accepted_records, rejected_records) — schema validation failure
- Date field not in YYYY-MM-DD format — pattern validation error
- Numeric values outside allowed range (±1,000,000,000,000) — validation error
- Insufficient variance in data for meaningful correlation — degenerate result returned

## How this service works

Record routing — Two-measure correlation + Date by category pivot: Two-measure correlation + 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 two-measure correlation analysis between accepted_records and rejected_records across the supplied rows, and (2) a date-by-category pivot table grouping record counts by date and dataset_group. Both reports are computed locally on the supplied data with no external lookups. Up to 200 rows supported 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-analytics-two-measure-correlation-date-by-category-pivot-5b94e1a5/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)