# Issue Throughput — String Normalisation + Adjacent Row Changes

> Issue Throughput — 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-25).

Runs two analytical reports on issue throughput data: string normalisation of component/text fields and adjacent-row change detection for issues opened or closed metrics.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-software-13-029?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/issue-throughput-string-normalisation-adjacent-row-changes-3961a319
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e1Fw7ECtGWgPrqkS5VXOM

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 issue-throughput-string-normalisation-adjacent-row-changes-3961a319 -d '<json body>'
```

Example prompt: Can you run string normalisation and adjacent row change detection on my issue throughput data? I have daily records for two components — group-a and group-b — with issues_opened values, and I want both reports covering up to 200 rows.

## When to prefer this

Choose this endpoint when you have issue throughput records (issues opened/closed) that need both text field standardisation and sequential row-change analysis in a single low-cost call. It is purpose-built for software engineering metrics with a specific schema, so prefer it over general-purpose analytics when your data matches the issues_opened/issues_closed structure.

## Known failure modes

- Input array exceeds 200 rows — request will be rejected or truncated
- Missing required fields (row_id, component, date, issues_opened, issues_closed) cause validation errors
- Invalid date format (not YYYY-MM-DD) causes schema rejection
- Numeric values outside allowed range trigger validation failure
- Empty rows array returns an error

## How this service works

Issue throughput — String normalisation + Adjacent row changes: String normalisation + Adjacent row changes for supplied issue throughput records (issues_opened, issues_closed). 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 per call: (1) a string normalisation report identifying and standardising inconsistent text values in component and related fields, and (2) an adjacent row changes report showing differences between consecutive rows for the selected metric (issues_opened or issues_closed). Covers up to 200 input rows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "component",
     "date",
     "issues_opened",
     "issues_closed"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "component": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "issues_closed": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "issues_opened": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "component": "group-a",
     "issues_closed": 1,
     "issues_opened": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "component": "group-b",
     "issues_closed": 2,
     "issues_opened": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "component": "group-a",
     "issues_closed": 3,
     "issues_opened": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "component": "group-b",
     "issues_closed": 4,
     "issues_opened": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "issues_opened",
    "issues_closed"
   ],
   "type": "string",
   "default": "issues_opened"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/issue-throughput-string-normalisation-adjacent-row-changes-3961a319/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)