# Transaction Fee Observations — Numeric Interval Filter + Adjacent Row Changes

> Transaction Fee Observations — Numeric Interval Filter + 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-29).

Applies a numeric interval filter and computes adjacent row changes on user-supplied transaction fee observation records (fee_units, transaction_count), returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-03-127?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-numeric-interval-filter-adjacent-row-dad1f6a5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Mb5nwc14ruCs6gzfut5A2

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-numeric-interval-filter-adjacent-row-dad1f6a5 -d '<json body>'
```

Example prompt: I have a set of transaction fee observations with columns row_id, instrument_group, date, fee_units, and transaction_count — can you run the numeric interval filter (keeping fee_units between 10 and 50) and the adjacent row changes report on these rows for me? Here are up to 200 rows of data.

## When to prefer this

Choose this endpoint when you have pre-collected transaction fee observation data (up to 200 rows) and need both a numeric range filter and adjacent row delta analysis in a single low-cost call. It is not a live data feed or prediction service — it is a local analytical engine operating purely on supplied data. Prefer it over general-purpose analytics when you specifically need the combination of interval filtering and row-over-row change detection on fee_units or transaction_count fields.

## Known failure modes

- Input exceeds 200 rows — request will be rejected or truncated
- Missing required fields (row_id, date, fee_units, transaction_count, instrument_group) cause validation errors
- Date values not matching YYYY-MM-DD pattern result in schema rejection
- Minimum greater than maximum produces empty interval filter results
- Null numeric values in the selected field may be excluded from or cause errors in adjacent row change computation
- Payment of 0.01 USDC not completed — endpoint returns 402 without processing

## How this service works

Transaction fee observations — Numeric interval filter + Adjacent row changes: Numeric interval filter + 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) rows from the submitted dataset whose selected field (fee_units or transaction_count) falls within the specified [minimum, maximum] interval; and (2) adjacent row change values showing the delta between consecutive rows for the selected field. Up to 200 input rows processed 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"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transaction-fee-observations-numeric-interval-filter-adjacent-row-dad1f6a5/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)