# Crop Yield Records — Keyed Dataset Comparison

> Crop Yield 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-16).

Compares two sets of crop yield records (matched by row key) and returns local descriptive analytics highlighting differences between them.

## Facts

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

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 crop-yield-records-keyed-dataset-comparison-86c49cf3 -d '<json body>'
```

Example prompt: Compare these two sets of crop yield records for me — my baseline has wheat on 2024-06-01 with 50 hectares and 12000 kg harvest, and my updated set has the same row but 55 hectares and 13500 kg harvest — give me a keyed comparison report showing what changed.

## When to prefer this

Choose this endpoint when you have two structured crop yield datasets keyed by row_id and want a fast, local descriptive comparison of numeric field differences (hectares, harvest_kg) without needing forecasting, enrichment, or external data. It is ideal for season-over-season comparisons, data quality audits between record versions, or pre/post intervention analysis on up to 200 records per dataset. At $0.01 USDC per call it is cost-effective for frequent or automated comparison tasks.

## Known failure modes

- Rows with duplicate row_id values within a single dataset may cause undefined comparison behavior
- Missing required fields (row_id, crop, date, hectares, harvest_kg) will cause validation errors
- Exceeding 200 rows in either dataset will be rejected
- Malformed date strings not matching YYYY-MM-DD pattern will fail schema validation
- Empty primary dataset (rows array) will be rejected; secondary dataset (other) may be empty

## How this service works

Crop yield records - Keyed dataset comparison: Keyed dataset comparison for Crop yield 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 containing descriptive analytics for up to 200 matched crop yield record pairs. The report highlights per-key differences in numeric fields (hectares, harvest_kg) between the primary and comparison datasets, including summaries of changes, counts of matched/unmatched rows, and local statistical descriptors. No forecasting or external data enrichment is included.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/crop-yield-records-keyed-dataset-comparison-86c49cf3/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)