# Issue Throughput Numeric Row Ordering and Keyed Dataset Comparison

> Issue Throughput Numeric Row Ordering and Keyed Dataset Comparison 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).

Ranks issue throughput rows numerically and compares two keyed datasets of issues_opened/issues_closed data, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-software-13-123?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-numeric-row-ordering-and-keyed-dataset-comparison-521a0be8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oOz08umTaCin3WYAu39bw

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-numeric-row-ordering-and-keyed-dataset-comparison-521a0be8 -d '<json body>'
```

Example prompt: Rank these issue throughput rows by issues_opened and also compare them against last sprint's dataset to see what changed — I have up to 50 rows for each period with fields row_id, component, date, issues_opened, and issues_closed.

## When to prefer this

Choose this endpoint when you need both a ranked ordering of issue throughput rows AND a side-by-side keyed comparison of two issue datasets in a single call at minimal cost. Ideal for sprint retrospectives, release comparisons, or component-level issue volume analysis where all data is already available locally and no live data fetching or prediction is needed.

## Known failure modes

- Row count exceeds 200 items — request will be rejected or truncated
- Missing required fields (row_id, component, date, issues_opened, issues_closed) cause validation errors
- Invalid date format (must be YYYY-MM-DD) causes schema rejection
- Null numeric values may affect ranking order
- Mismatched row_ids between primary and secondary datasets may produce incomplete comparison results
- Payment of 0.01 USDC not provided causes 402 rejection

## How this service works

Issue throughput — Numeric row ordering + Keyed dataset comparison: Numeric row ordering + Keyed dataset comparison 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: (1) the input rows sorted numerically by the chosen field (issues_opened or issues_closed), and (2) a keyed comparison between the primary and secondary datasets highlighting differences by row_id, both computed locally without any external lookup.

## 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"
  },
  "other": {
   "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": 1000000000
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/issue-throughput-numeric-row-ordering-and-keyed-dataset-comparison-521a0be8/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)