# Accessibility Findings — Two-Measure Correlation + Secondary-Measure Weighted Mean

> Accessibility Findings — Two-Measure Correlation + Secondary-Measure Weighted Mean is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-02).

Computes Pearson/rank correlation between two accessibility metrics and a weighted mean of a secondary measure across up to 200 supplied accessibility findings records, returning two independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-game-17-181?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/accessibility-findings-two-measure-correlation-secondary-measure-24b9ceae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xl2uKmwbpK2l5RLUkfICz

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 accessibility-findings-two-measure-correlation-secondary-measure-24b9ceae -d '<json body>'
```

Example prompt: I have accessibility audit data for my game with findings and resolved_findings counts across several areas — can you run a two-measure correlation plus a weighted mean on the resolved_findings field for these rows: [{"row_id":"row-1","date":"2026-10-01","game_area":"group-a","findings":10,"resolved_findings":1},{"row_id":"row-2","date":"2026-10-02","game_area":"group-b","findings":20,"resolved_findings":2}]?

## When to prefer this

Choose this endpoint when you have up to 200 rows of accessibility findings data with both a raw findings count and a resolved_findings count, and you need both a correlation analysis between those two measures AND a weighted mean of one of them in a single paid call. It is a local analytical engine — no external data enrichment, live lookups, or predictions are performed, making it fast and deterministic. Prefer alternatives if you need more than 200 rows, require ML-based predictions, or need only a single statistic rather than both reports.

## Known failure modes

- Fewer than 1 row supplied — request rejected
- More than 200 rows supplied — request rejected (maxItems limit)
- Missing required fields (row_id, game_area, date, findings, resolved_findings) in any row — validation error
- Invalid date format (not YYYY-MM-DD) — schema validation failure
- Field enum value not 'findings' or 'resolved_findings' — validation error
- All values null for selected field — correlation or weighted mean cannot be computed
- Payment not included or insufficient (must be 0.01 USDC via x402) — payment error

## How this service works

Accessibility findings — Two-measure correlation + Secondary-measure weighted mean: Two-measure correlation + Secondary-measure weighted mean for supplied accessibility findings records (findings, resolved_findings). 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) a Pearson or rank correlation coefficient between the 'findings' and 'resolved_findings' columns across all supplied rows, and (2) a weighted mean of the selected secondary measure (findings or resolved_findings) — both computed locally on the supplied data with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/accessibility-findings-two-measure-correlation-secondary-measure-24b9ceae/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)