# Specification Traceability — Category Frequencies + Two-Measure Correlation

> Specification Traceability — Category Frequencies + 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-24).

Analyzes specification traceability records by computing category frequencies across document groups and calculating the correlation between mapped_requirements and total_requirements for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-writing-21-108?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/specification-traceability-category-frequencies-two-measure-correlation-30fa9c08
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OQMbTMOEmNdSx18XOtW9N

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 specification-traceability-category-frequencies-two-measure-correlation-30fa9c08 -d '<json body>'
```

Example prompt: I have a list of specification traceability records with document groups, dates, and counts of mapped vs total requirements — can you run a category frequency breakdown by document group and compute the correlation between mapped_requirements and total_requirements across all rows?

## When to prefer this

Choose this endpoint when you have specification traceability records with numeric requirement counts and categorical document groupings and need both a distribution summary (frequencies) and a linear relationship measure (correlation) in a single low-cost call. Ideal for compliance teams, QA engineers, and requirements analysts who want a quick statistical snapshot without standing up their own analytics pipeline.

## Known failure modes

- Missing required fields (row_id, document_group, date, mapped_requirements, or total_requirements) cause row rejection or error
- Exceeding 200 rows returns an error or truncation
- Invalid date format (not YYYY-MM-DD) fails schema validation
- All-null values for either measure prevents correlation computation
- Fewer than 2 rows may make correlation undefined or meaningless

## How this service works

Specification traceability — Category frequencies + Two-measure correlation: Category frequencies + Two-measure correlation for supplied specification traceability records (mapped_requirements, total_requirements). 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) a frequency count of records per document_group category, and (2) a Pearson or equivalent correlation coefficient between the mapped_requirements and total_requirements numeric columns, computed locally on the supplied rows without any external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/specification-traceability-category-frequencies-two-measure-correlation-30fa9c08/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)