# Rig Complexity — Numeric Row Ordering + Keyed Dataset Comparison

> Rig Complexity — Numeric Row Ordering + 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-31).

Sorts rig complexity records by bone_count or constraint_count and compares two supplied datasets by shared row keys, returning two analytical reports for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-creative-04-123?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rig-complexity-numeric-row-ordering-keyed-dataset-comparison-5698138c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mHCQtzbJoB7-ggebYRuZE

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 rig-complexity-numeric-row-ordering-keyed-dataset-comparison-5698138c -d '<json body>'
```

Example prompt: Sort these 50 rig records by bone_count and compare them against our baseline dataset using the same row IDs — I want both the ordered ranking and a keyed comparison report showing where values differ.

## When to prefer this

Choose this endpoint when you have structured rig complexity data (bone_count, constraint_count) already in hand and need both a numeric sort and a side-by-side keyed comparison between two datasets in a single $0.01 call. Ideal for animation pipeline QA, pre-release audits, or tracking rig changes between builds. Not suitable when you need live data retrieval, predictive modeling, or professional rigging assessment.

## Known failure modes

- Exceeds 200-row limit — request rejected or truncated
- Missing required fields (row_id, date, bone_count, constraint_count) — validation error
- Invalid date format (not YYYY-MM-DD) — schema rejection
- row_id mismatch between rows and other arrays — comparison report may show unmatched keys
- Null numeric values may affect sort ordering
- Invalid field enum value (not bone_count or constraint_count) — error response

## How this service works

Rig complexity — Numeric row ordering + Keyed dataset comparison: Numeric row ordering + Keyed dataset comparison for supplied rig complexity records (bone_count, constraint_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 independent analytical reports: (1) the input rows sorted numerically by the selected field (bone_count or constraint_count), and (2) a keyed comparison between the primary rows array and the other rows array matched by row_id, highlighting value differences. Both reports are generated locally without external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rig-complexity-numeric-row-ordering-keyed-dataset-comparison-5698138c/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)