# Transaction Fee Observations — String Normalisation + Adjacent Row Changes

> Transaction Fee Observations — String Normalisation + 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-26).

Applies string normalisation and adjacent row change analysis to up to 200 transaction fee observation records, returning two local analytical reports on fee_units or transaction_count fields.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-finance-03-029?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-string-normalisation-adjacent-row-changes-5d72912c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wjOA1piHrAGg0Grvt0eKH

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-string-normalisation-adjacent-row-changes-5d72912c -d '<json body>'
```

Example prompt: Can you run string normalisation and adjacent row change analysis on these transaction fee records — I have 4 rows with fee_units and transaction_count for instrument groups group-a and group-b from October 2026, and I want the analysis focused on fee_units?

## When to prefer this

Choose this endpoint when you have up to 200 transaction fee observation records and need both string normalisation and adjacent row change analysis in a single low-cost call ($0.01 USDC). It is best suited for offline/batch analytical reporting on supplied data rather than live lookups or predictive analytics. Prefer it when you need two complementary reports (normalisation + delta) on the same dataset without calling separate endpoints.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, date, instrument_group, fee_units, transaction_count) causes rejection
- Invalid date format (non-YYYY-MM-DD) triggers a schema validation error
- Numeric values outside ±1,000,000,000,000 are rejected
- Empty rows array returns an error
- Invalid field enum value (not fee_units or transaction_count) causes failure

## How this service works

Transaction fee observations — String normalisation + Adjacent row changes: String normalisation + 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

Two analytical reports: one covering string normalisation of the instrument_group and related text fields, and one covering adjacent (row-to-row) change values for the selected numeric field (fee_units or transaction_count), applied to up to 200 supplied input rows. No external data or predictions are included.

## 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-string-normalisation-adjacent-row-changes-5d72912c/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)