# Transaction Fee Observations — Daily Sum Series + Adjacent Row Changes

> Transaction Fee Observations — Daily Sum Series + Adjacent Row Changes 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-25).

Computes a daily sum time series and adjacent row-to-row change report for supplied transaction fee observation records (fee_units or transaction_count).

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-03-137?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transaction-fee-observations-daily-sum-series-adjacent-row-changes-02a80f35
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xy6tOWjdH-jHL5rpleK2N

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-daily-sum-series-adjacent-row-changes-02a80f35 -d '<json body>'
```

Example prompt: Can you run a daily sum series and adjacent row change report on my transaction fee data? I have 4 rows with fee_units values of 10, 20, 15, 30 for dates 2026-10-01 through 2026-10-04, and I want to analyze the fee_units field.

## When to prefer this

Use this endpoint when you have raw transaction fee observation records and need both a daily aggregated sum time series and a consecutive-row delta report in a single call. It is ideal for offline/batch analytical workflows where you supply your own data (no live data fetched) and need two complementary reports cheaply. Prefer this over general-purpose analytics tools when working with the specific fee_units/transaction_count schema and needing deterministic local computation.

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Missing required fields (row_id, date, instrument_group, fee_units, transaction_count) — validation error
- Invalid date format (must match YYYY-MM-DD pattern) — schema validation failure
- Numeric values outside ±1,000,000,000,000 range — schema validation failure
- Empty rows array — minimum 1 item required

## How this service works

Transaction fee observations — Daily sum series + Adjacent row changes: Daily sum series + Adjacent row changes 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 daily sum series aggregating the chosen field (fee_units or transaction_count) by date, and (2) an adjacent row change report showing the difference between consecutive observations. Up to 200 input rows supported per call.

## 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-daily-sum-series-adjacent-row-changes-02a80f35/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)