# Travel Administration: Two-Measure Correlation + Keyed Dataset Comparison

> Travel Administration: Two-Measure Correlation + 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-26).

Computes Pearson correlation between trip_count and recorded_cost, and performs a keyed row-by-row comparison between two travel administration datasets (up to 200 rows each).

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-operations-14-183?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/travel-administration-two-measure-correlation-keyed-dataset-comparison-3fc395f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QXUxfNd937JmOQSK6Xya9

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 travel-administration-two-measure-correlation-keyed-dataset-comparison-3fc395f7 -d '<json body>'
```

Example prompt: Can you run a correlation analysis between trip_count and recorded_cost across my travel records, and also compare them against last month's dataset to flag any row-level differences? I have up to 80 rows in each dataset, keyed by row_id.

## When to prefer this

Choose this endpoint when you need both a statistical correlation between two numeric travel metrics and a structural diff between two versions of the same dataset in a single API call. It is ideal for travel expense audits, policy-change impact assessments, or periodic data quality checks on corporate travel records — particularly when working with up to 200 rows and wanting two distinct analytical outputs from one request at a low flat fee.

## Known failure modes

- Exceeds 200-row limit — request rejected or truncated
- Missing required fields (row_id, trip_count, recorded_cost) — validation error
- Null values in numeric fields may affect correlation computation
- row_id mismatch between datasets results in unmatched rows flagged
- Malformed date strings not matching YYYY-MM-DD pattern cause schema validation failure
- Empty rows array rejected (minItems: 1)

## How this service works

Travel administration — Two-measure correlation + Keyed dataset comparison: Two-measure correlation + Keyed dataset comparison for supplied travel administration records (trip_count, recorded_cost). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.

## Output

Returns two analytical reports: (1) a Pearson correlation result between trip_count and recorded_cost across the primary dataset, and (2) a keyed comparison report showing row-level matches, mismatches, and value differences between the primary and secondary datasets, based on row_id as the join key.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/travel-administration-two-measure-correlation-keyed-dataset-comparison-3fc395f7/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)