# Transaction Fee Observations — Daily Sum Series + Base-100 Series

> Transaction Fee Observations — Daily Sum Series + Base-100 Series 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 daily sum time series and Base-100 index series for user-supplied transaction fee observation records, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-03-138?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-daily-sum-series-base-100-series-34bd859d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iZaHZWIGvvuWGTSldZRuS

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-base-100-series-34bd859d -d '<json body>'
```

Example prompt: Can you generate both a daily sum series and a Base-100 index (rebased at row 0) for my transaction fee data — I have records with date, fee_units, transaction_count, and instrument_group for about 50 rows — and I want to analyze the fee_units field?

## When to prefer this

Choose this endpoint when you have pre-collected transaction fee observation records and need both a daily aggregated sum series and a normalized Base-100 trend index in a single paid call — without requiring an external data source, live lookup, or prediction. Ideal for finance analytics workflows where you supply your own rows (up to 200) and want two complementary time-series reports computed locally and returned immediately.

## Known failure modes

- Missing required fields (row_id, date, fee_units, transaction_count, instrument_group) returns a validation error
- Date values not matching YYYY-MM-DD pattern are rejected
- More than 200 rows submitted exceeds the maxItems limit and is rejected
- base_index out of range (>= number of rows) causes an indexing error
- Null values in fee_units or transaction_count may affect sum/index calculations
- Payment of 0.01 USDC not completed causes request to be rejected with 402

## How this service works

Transaction fee observations — Daily sum series + Base-100 series: Daily sum series + Base-100 series 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

Two independent analytical reports: (1) a daily sum series aggregating the selected field (fee_units or transaction_count) by date, and (2) a Base-100 index series rebasing the selected field to 100 at the specified row index — both computed locally from the supplied records, up to 200 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-daily-sum-series-base-100-series-34bd859d/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)