# Internal Support — Numeric Row Ordering + Two-Measure Correlation

> Internal Support — Numeric Row Ordering + Two-Measure Correlation 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 support records by a chosen numeric field and computes the correlation between responded_requests and received_requests for up to 200 rows of internal support data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-operations-22-120?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/internal-support-numeric-row-ordering-two-measure-correlation-edccae9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6H8HdHBZr5BATsKh2lSx4

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 internal-support-numeric-row-ordering-two-measure-correlation-edccae9c -d '<json body>'
```

Example prompt: I have daily support records for two teams with responded_requests and received_requests counts — can you rank the rows by responded_requests and also compute the correlation between responded and received requests across all 200 rows?

## When to prefer this

Choose this endpoint when you have up to 200 rows of internal support records with responded_requests and received_requests columns and need both a numeric sort/ranking and a two-measure correlation in a single $0.01 call. It is ideal for lightweight, self-contained analytics on already-collected support data where no live data fetching, prediction, or external enrichment is needed. Prefer alternatives if you need more than 200 rows, more than two measures correlated, or real-time ticket data integration.

## Known failure modes

- Missing required fields (row_id, date, responded_requests, received_requests) causes validation error
- More than 200 rows submitted exceeds the maxItems limit and will be rejected
- Invalid date format (not YYYY-MM-DD) fails schema validation
- Both numeric fields null for all rows may produce undefined or null correlation
- Invalid enum value for field parameter (must be responded_requests or received_requests)
- Empty rows array rejected due to minItems:1 constraint

## How this service works

Internal support — Numeric row ordering + Two-measure correlation: Numeric row ordering + Two-measure correlation for supplied internal support records (responded_requests, received_requests). 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 ordered numerically by the selected field (responded_requests or received_requests), and (2) a correlation measure between the two numeric fields (responded_requests and received_requests) computed across all supplied rows. Both reports are derived entirely from the submitted data with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/internal-support-numeric-row-ordering-two-measure-correlation-edccae9c/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)