# Time Entries Keyed Dataset Comparison

> Time Entries 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-15).

Compares two keyed datasets of time entry records (up to 200 rows each) and returns data-quality and numeric difference analysis between them.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-analytics-time-entries-compare?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/time-entries-keyed-dataset-comparison-b5d4556a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0eslKODclaN_VWzJkBbZz

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 time-entries-keyed-dataset-comparison-b5d4556a -d '<json body>'
```

Example prompt: Compare these two sets of time entries for me — the original has row-1 through row-4 with 10, 20, 15, and 30 hours logged across group-a and group-b projects, and the updated version has the same rows but with 10, 21, 17, and 33 hours — tell me what changed in total hours and billable hours.

## When to prefer this

Choose this endpoint when you need a structured, keyed comparison of two time entry datasets (up to 200 rows) with numeric delta analysis, particularly for timesheet auditing, billing reconciliation, or data migration validation. It performs local numeric and data-quality processing without external enrichment, making it fast and deterministic. Prefer this over generic diff tools when your data is specifically time entries with project, date, hours, and billable_hours fields.

## Known failure modes

- Rows array exceeds 200 items — request rejected with validation error
- Missing required fields (row_id, project, date, hours, billable_hours) on any row — schema validation failure
- Invalid date format (not YYYY-MM-DD) — pattern validation error
- Numeric values outside allowed range — validation error
- Empty rows array — minItems constraint violation
- Mismatched row_ids between datasets resulting in all-unmatched comparison

## How this service works

Time entries - Keyed dataset comparison: Keyed dataset comparison for Time entries. 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 keyed dataset comparison deliverable that includes per-row numeric differences in hours and billable_hours fields, matched/unmatched row identification by row_id, and data-quality metrics across the two supplied time entry arrays.

## Request schema (JSON Schema)

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

## More

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