# Transaction Fee Observations — Base-100 Series + Date-by-Category Pivot

> Transaction Fee Observations — Base-100 Series + 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-26).

Generates two local analytical reports (Base-100 indexed series and date-by-category pivot table) from user-supplied transaction fee observation records, covering fee_units or transaction_count metrics.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-03-167?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/transaction-fee-observations-base-100-series-date-by-category-pivot-41ccb811
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rGUrtIEDqhQRrNFn_oK9r

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-base-100-series-date-by-category-pivot-41ccb811 -d '<json body>'
```

Example prompt: I have transaction fee data for two instrument groups over four days — group-a had fee_units of 10, 15 and group-b had 20, 30 on dates 2026-10-01 through 2026-10-04, with transaction counts 1, 3 and 2, 4 respectively. Can you run the Base-100 series and date-by-category pivot on the fee_units field, starting the index at row 0?

## When to prefer this

Choose this endpoint when you have up to 200 rows of transaction fee observation records with instrument_group and date dimensions, and need both a normalized Base-100 trend series and a date-by-category pivot computed from your own supplied data — no external data fetch or live market lookup needed. Prefer it over general analytics tools when you want a fixed-cost ($0.01 USDC), deterministic, offline computation that returns two reports in a single call.

## Known failure modes

- More than 200 rows submitted — request will be rejected due to maxItems constraint
- Missing required row fields (row_id, instrument_group, date, fee_units, transaction_count) — validation error
- Invalid date format (not YYYY-MM-DD pattern) — schema validation failure
- base_index out of bounds (references a row that doesn't exist in the submitted data) — computation error
- Numeric values outside allowed range (beyond ±1,000,000,000,000) — validation rejection
- Empty rows array — minItems:1 constraint violated

## How this service works

Transaction fee observations — Base-100 series + Date by category pivot: Base-100 series + 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 computed locally from the supplied data: (1) a Base-100 indexed time series for the selected field (fee_units or transaction_count) anchored at the specified base_index row, showing relative change across dates and instrument groups; (2) a date-by-category pivot table cross-tabulating the selected metric by date and instrument_group. Supports up to 200 input rows.

## 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"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transaction-fee-observations-base-100-series-date-by-category-pivot-41ccb811/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)