# Content Engagement Keyed Dataset Comparison

> Content Engagement 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 keyed datasets of content engagement metrics (views and engagements by content type and date) row-by-row, returning numeric difference analysis and data-quality results.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-analytics-content-engagement-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/content-engagement-keyed-dataset-comparison-15840e33
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CQZshO61A96CcMZ7nrZFr

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 content-engagement-keyed-dataset-comparison-15840e33 -d '<json body>'
```

Example prompt: Compare these two sets of content engagement data for me — my baseline dataset has rows for 'article' and 'video' content types with their daily views and engagements from last month, and I want to see how they differ from this week's numbers row by row.

## When to prefer this

Choose this endpoint when you need a fast, local, row-keyed numeric comparison of two content engagement datasets (up to 200 rows each) without any external API calls or enrichment. It is ideal for A/B test result diffing, before/after campaign comparisons, or validating consistency between two analytics exports. Prefer alternatives if you need forecasting, external benchmarking, or datasets larger than 200 rows.

## Known failure modes

- Empty or missing 'rows' array returns validation error
- Row count exceeds 200 items per dataset — request rejected
- Mismatched row_id keys between datasets may produce unmatched comparison entries
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Null numeric values for views or engagements are accepted but may affect delta computation
- Missing required fields (row_id, content_type, date, views, engagements) causes rejection

## How this service works

Content engagement - Keyed dataset comparison: Keyed dataset comparison for Content engagement. 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

Returns a bounded comparison deliverable containing row-keyed numeric differences between the two input datasets, including delta values for views and engagements per content type and date, along with data-quality flags for missing or anomalous records. No external enrichment or forecasting is applied — all processing is local and numeric.

## Request schema (JSON Schema)

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

## More

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