# Rig Complexity Base-100 Series + Keyed Dataset Comparison

> Rig Complexity Base-100 Series + 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-17).

Computes a Base-100 indexed series and a keyed dataset comparison report for supplied 3D rig complexity metrics (bone_count, constraint_count) across up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-creative-04-168?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rig-complexity-base-100-series-keyed-dataset-comparison-a4869ff6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jtOjzYEpPYb3VgTSFl6H8

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-base-100-series-keyed-dataset-comparison-a4869ff6 -d '<json body>'
```

Example prompt: I have two sets of rig complexity records for my character assets — group-a and group-b — with bone_count and constraint_count logged by date. Can you run a Base-100 series and a keyed dataset comparison on bone_count for up to 200 rows across both datasets?

## When to prefer this

Choose this endpoint when you need to normalize 3D rig complexity metrics to a common baseline (Base-100) and simultaneously compare two datasets by key — especially when working with bone_count or constraint_count records grouped by asset group and date. Prefer this over generic statistics tools when the domain is character/rig pipelines and you need both a trend index and a side-by-side keyed diff in a single low-cost call ($0.01 USDC for both reports).

## Known failure modes

- Missing required fields (row_id, date, bone_count, constraint_count) returns a validation error
- Exceeding 200 rows in either dataset causes a rejection
- Invalid date format (not YYYY-MM-DD) fails pattern validation
- Null values in the selected numeric field may produce incomplete series results
- Mismatched row_ids between primary and comparison dataset reduce keyed comparison coverage

## How this service works

Rig complexity — Base-100 series + Keyed dataset comparison: Base-100 series + 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 analytical reports: (1) a Base-100 indexed series rebasing the selected field (bone_count or constraint_count) relative to the first data point, and (2) a keyed dataset comparison highlighting row-level and group-level differences between the primary and secondary datasets. No external lookups or predictions are made — all analysis uses the supplied data only.

## 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-base-100-series-keyed-dataset-comparison-a4869ff6/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)