# Delivery Timing - Keyed Dataset Comparison

> Delivery Timing - Keyed Dataset Comparison 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-18).

Compares two keyed datasets of delivery timing records row-by-row, reporting differences in delivery minutes and distance across matched record IDs and routes.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-analytics-delivery-timing-compare?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delivery-timing-keyed-dataset-comparison-fbc03f11
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P1-MKALRT3fNnzD8XkaGV

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 delivery-timing-keyed-dataset-comparison-fbc03f11 -d '<json body>'
```

Example prompt: Compare my two delivery timing datasets — the baseline has routes group-a and group-b with delivery minutes and distance_km keyed by row IDs row-1 through row-4 for October 2026, and the comparison dataset has the same keys but slightly different delivery_minutes values. Give me a row-by-row diff of what changed.

## When to prefer this

Choose this endpoint when you need a structured, row-level numeric comparison between two keyed delivery timing datasets — especially when records share the same IDs across both datasets and you want to detect changes in delivery_minutes or distance_km without any external API calls or forecasting. Ideal for before/after analysis, carrier reconciliation, or weekly drift checks on up to 200 records at $0.01 per call.

## Known failure modes

- Empty rows array (minItems:1 violated) returns validation error
- row_id missing or blank on any record causes schema rejection
- Exceeding 200 records in either dataset returns a bounds error
- date strings not matching YYYY-MM-DD pattern cause validation failure
- Non-numeric values for delivery_minutes or distance_km (where null not intended) may cause computation errors
- Mismatched row_id keys between datasets result in unmatched/orphan record entries in output

## How this service works

Delivery timing - Keyed dataset comparison: Keyed dataset comparison for Delivery timing. Up to 200 supplied typed records. Local numeric and data-quality processing; no external enrichment or forecasting. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded keyed dataset comparison deliverable.

## Output

A keyed comparison deliverable that matches records across both datasets by row_id, reporting per-record differences in delivery_minutes and distance_km, along with data quality observations. Results are computed locally with no external enrichment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "route",
     "date",
     "delivery_minutes",
     "distance_km"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "route": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "distance_km": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "delivery_minutes": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "route": "group-a",
     "row_id": "row-1",
     "distance_km": 1,
     "delivery_minutes": 10
    },
    {
     "date": "2026-10-02",
     "route": "group-b",
     "row_id": "row-2",
     "distance_km": 2,
     "delivery_minutes": 20
    },
    {
     "date": "2026-10-03",
     "route": "group-a",
     "row_id": "row-3",
     "distance_km": 3,
     "delivery_minutes": 15
    },
    {
     "date": "2026-10-04",
     "route": "group-b",
     "row_id": "row-4",
     "distance_km": 4,
     "delivery_minutes": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "other": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "route",
     "date",
     "delivery_minutes",
     "distance_km"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "route": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "distance_km": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "delivery_minutes": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "route":
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delivery-timing-keyed-dataset-comparison-fbc03f11/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)