# Fleet Fuel Records – Keyed Dataset Comparison

> Fleet Fuel Records – 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-19).

Compares two sets of fleet fuel records (up to 200 rows each) by matching on row keys and computing descriptive analytics on differences in distance and fuel consumption.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-fleet-fuel-records-compare?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fleet-fuel-records-keyed-dataset-comparison-513dfb90
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cFdwVFaks8OzeKvy5dEQR

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 fleet-fuel-records-keyed-dataset-comparison-513dfb90 -d '<json body>'
```

Example prompt: Compare these two sets of fleet fuel records for me — the baseline has vehicle group-a doing 10 km on 1 litre on 2026-10-01 and group-b doing 20 km on 2 litres on 2026-10-02, and the comparison dataset has the same row IDs but group-b logged 21 km and 33 km instead — give me a keyed comparison report showing where the numbers differ.

## When to prefer this

Choose this endpoint when you have two structured, row-keyed fleet fuel datasets (up to 200 rows each) and need a fast, local descriptive comparison — e.g. period-over-period analysis, source reconciliation, or group benchmarking — without requiring AI enrichment, external data, or forecasting. Prefer this over general analytics tools when you specifically need a matched-key diff with fleet fuel schema (vehicle, date, distance_km, fuel_litres).

## Known failure modes

- Missing required fields (row_id, vehicle, date, distance_km, fuel_litres) cause validation errors
- Date strings not matching YYYY-MM-DD pattern are rejected
- Exceeding 200 rows per array causes a schema violation
- row_id values that appear in only one dataset may be flagged as unmatched
- Null numeric values may reduce the richness of computed statistics
- Payment failure (insufficient USDC) blocks the request

## How this service works

Fleet fuel records - Keyed dataset comparison: Keyed dataset comparison for Fleet fuel records. Up to 200 supplied typed records. Local descriptive analytics; no enrichment or forecast. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded keyed dataset comparison report.

## Output

A bounded keyed dataset comparison report that matches records across both input arrays by row_id and computes per-row and aggregate descriptive analytics — including numeric differences, summary statistics, and vehicle-level breakdowns — for distance_km and fuel_litres fields. No external enrichment or forecasting is included.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fleet-fuel-records-keyed-dataset-comparison-513dfb90/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)