# Table Extraction — Two-Measure Correlation + Keyed Dataset Comparison > Table Extraction — Two-Measure Correlation + 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-30). Analyzes table extraction records by computing correlation between extracted_rows and expected_rows, and comparing two keyed datasets side-by-side, returning two independent analytical reports for up to 200 rows. ## Facts - Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-web-10-183?utm_source=zero.xyz - Price: $0.01/call - Payment: x402 - Status: unknown - Last checked: 2026-10-30 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/table-extraction-two-measure-correlation-keyed-dataset-comparison-f015474d - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mqgkAaXSHyi70Ut9L_hLP 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 table-extraction-two-measure-correlation-keyed-dataset-comparison-f015474d -d '' ``` Example prompt: Can you run a correlation and keyed comparison on my table extraction results? I have two datasets — my primary run and a reference run — each with up to 50 rows identified by row_id, site_group, and date, showing extracted_rows versus expected_rows. I want both reports at once. ## When to prefer this Choose this endpoint when you need to simultaneously assess extraction accuracy (via correlation) and directly compare two table extraction runs key-by-key for up to 200 records at a fixed $0.01 cost. It is ideal for QA workflows, ETL regression checks, and scraping pipeline audits where both statistical agreement and row-level discrepancy detection are needed in a single call. Prefer it over generic statistics services when your data is already structured as table extraction records with row_id, site_group, date, extracted_rows, and expected_rows fields. ## Known failure modes - Input exceeds 200 rows — request will be rejected or truncated - Missing required fields (row_id, date, extracted_rows, expected_rows) cause validation errors - Date fields not matching YYYY-MM-DD pattern will fail schema validation - Null values in extracted_rows or expected_rows may affect correlation calculation - Mismatched row_ids between primary and comparison datasets reduce keyed comparison coverage - Both 'rows' and 'other' arrays must be supplied; missing one yields incomplete reports ## How this service works Table extraction — Two-measure correlation + Keyed dataset comparison: Two-measure correlation + Keyed dataset comparison for supplied table extraction records (extracted_rows, expected_rows). 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 two-measure correlation report quantifying the statistical relationship between extracted_rows and expected_rows across all supplied records, and (2) a keyed dataset comparison report matching records from the primary and secondary datasets by row_id to identify discrepancies. No external data is fetched; all analysis is performed locally on the supplied data. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "rows": { "type": "array", "items": { "type": "object", "required": [ "row_id", "site_group", "date", "extracted_rows", "expected_rows" ], "properties": { "date": { "type": "string", "default": "", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "maxLength": 10 }, "row_id": { "type": "string", "default": "", "maxLength": 80, "minLength": 1 }, "site_group": { "type": "string", "default": "", "maxLength": 80 }, "expected_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 }, "extracted_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 } }, "additionalProperties": false }, "default": [ { "date": "2026-10-01", "row_id": "row-1", "site_group": "group-a", "expected_rows": 1, "extracted_rows": 10 }, { "date": "2026-10-02", "row_id": "row-2", "site_group": "group-b", "expected_rows": 2, "extracted_rows": 20 }, { "date": "2026-10-03", "row_id": "row-3", "site_group": "group-a", "expected_rows": 3, "extracted_rows": 15 }, { "date": "2026-10-04", "row_id": "row-4", "site_group": "group-b", "expected_rows": 4, "extracted_rows": 30 } ], "maxItems": 200, "minItems": 1 }, "other": { "type": "array", "items": { "type": "object", "required": [ "row_id", "site_group", "date", "extracted_rows", "expected_rows" ], "properties": { "date": { "type": "string", "default": "", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "maxLength": 10 }, "row_id": { "type": "string", "default": "", "maxLength": 80, "minLength": 1 }, "site_group": { "type": "string", "default": "", "maxLength": 80 }, "expected_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 }, "extracted_rows": { "type": [ "number", "null" ], "maximum": 1000000000000, "minimum": -1000000000000 } }, "additionalProperties": false }, "default": [ { … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/table-extraction-two-measure-correlation-keyed-dataset-comparison-f015474d/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)