# Transaction Fee Observations — Two-Measure Correlation + Date by Category Pivot

> Transaction Fee Observations — Two-Measure Correlation + Date by Category Pivot 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-29).

Runs two local analytical reports on uploaded transaction fee data: a Pearson/Spearman-style correlation between fee_units and transaction_count, and a date-by-instrument-group pivot table, for up to 200 rows at $0.01 USDC.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-03-182?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transaction-fee-observations-two-measure-correlation-date-by-category-9b76b67c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TjjDkXH4Tx8uvqxrK9qyP

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 transaction-fee-observations-two-measure-correlation-date-by-category-9b76b67c -d '<json body>'
```

Example prompt: I have transaction fee observations for several instrument groups — can you run a correlation between fee_units and transaction_count, plus a pivot of fee_units by date and instrument group? Here are up to 200 rows with row_id, instrument_group, date, fee_units, and transaction_count fields.

## When to prefer this

Choose this endpoint when you have up to 200 rows of transaction fee observations with both fee_units and transaction_count and need two analyses in one call: a statistical correlation between those two measures AND a date-by-category pivot, all for a flat $0.01 USDC. It is ideal when data is already structured client-side and no live market data, predictions, or external lookups are needed — pure local computation on supplied rows.

## Known failure modes

- Input rows array is empty or missing — validation error
- Row count exceeds 200 — rejected with maxItems error
- Date fields not in YYYY-MM-DD format — pattern validation failure
- fee_units or transaction_count outside ±1,000,000,000,000 range — schema rejection
- Missing required fields (row_id, instrument_group, date) — validation error
- Payment of 0.01 USDC not completed via x402 protocol — 402 Payment Required
- All fee_units or transaction_count values are null — correlation undefined/empty result

## How this service works

Transaction fee observations — Two-measure correlation + Date by category pivot: Two-measure correlation + Date by category pivot for supplied transaction fee observations records (fee_units, transaction_count). 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 two-measure correlation analysis showing the statistical relationship between fee_units and transaction_count across the supplied rows, and (2) a date-by-category pivot table breaking down the selected measure (fee_units or transaction_count) by date and instrument_group. Both reports are computed locally on the supplied data without external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transaction-fee-observations-two-measure-correlation-date-by-category-9b76b67c/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)