# Record Routing Analytics — Numeric Interval Filter + Two-Measure Correlation

> Record Routing Analytics — Numeric Interval Filter + Two-Measure Correlation 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-15).

Filters record routing rows by a numeric interval on a chosen field and computes a two-measure correlation between accepted_records and rejected_records, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-analytics-19-131?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/record-routing-analytics-numeric-interval-filter-two-measure-25ccf44f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0CvQ4_mAwkusLdHcrXnDQ

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-interval-filter-two-measure-25ccf44f -d '<json body>'
```

Example prompt: I have 4 record routing rows with accepted_records and rejected_records per day across group-a and group-b — filter them to rows where accepted_records is between 10 and 25, and give me two reports including the correlation between accepted and rejected counts.

## When to prefer this

Choose this endpoint when you have tabular record routing data with accepted and rejected record counts and need both an interval-based row filter and a two-measure correlation in a single paid call. Ideal for lightweight ETL pipeline QA, data quality checks, or routing analytics where no external data enrichment or prediction is needed. At $0.01 USDC per call covering two reports on up to 200 rows, it is cost-effective for small-to-medium batch analytical tasks on pre-supplied data.

## Known failure modes

- More than 200 rows submitted — endpoint enforces a maxItems:200 limit and will reject oversized payloads
- minimum greater than maximum — logically invalid interval yields empty filter results or validation error
- Missing required fields (row_id, date, accepted_records, rejected_records) — schema validation failure
- date values not matching YYYY-MM-DD pattern — pattern validation error
- Both measures are null for all rows — correlation computation may return undefined or NaN

## How this service works

Record routing — Numeric interval filter + Two-measure correlation: Numeric interval filter + Two-measure correlation 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) rows from the input dataset that fall within the specified numeric interval on the chosen field, and (2) a correlation analysis between accepted_records and rejected_records across the filtered dataset. Covers up to 200 input rows 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"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/record-routing-analytics-numeric-interval-filter-two-measure-25ccf44f/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)