# Time Entries Two-Measure Correlation

> Time Entries 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-15).

Computes the two-measure (Pearson-style) correlation between hours and billable_hours across up to 200 time entry records, locally, with no external enrichment.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-analytics-time-entries-correlation?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/time-entries-two-measure-correlation-9b052227
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ni7meUkF8LB_OdKqpdey2

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 time-entries-two-measure-correlation-9b052227 -d '<json body>'
```

Example prompt: Can you run a two-measure correlation between total hours and billable hours on these time entries? I have 4 records: row-1 on 2026-10-01 for project group-a with 10 hours and 1 billable hour, row-2 on 2026-10-02 for group-b with 20 hours and 2 billable, row-3 on 2026-10-03 for group-a with 15 hours and 3 billable, and row-4 on 2026-10-04 for group-b with 30 hours and 4 billable.

## When to prefer this

Choose this endpoint when you need a fast, self-contained statistical correlation between two numeric measures (hours and billable_hours) in time entry records, without involving external APIs or enrichment. It is ideal for billing audits, timesheet analysis, or workforce analytics pipelines where you have up to 200 structured time-tracking rows and want a single correlation coefficient with data-quality signals at minimal cost ($0.01 USDC per call).

## Known failure modes

- Fewer than 1 row submitted — minimum items constraint violated
- More than 200 rows submitted — maxItems constraint exceeded
- Missing required fields (row_id, project, date, hours, billable_hours) on any row
- Date field not matching YYYY-MM-DD pattern — schema validation failure
- Null values in both numeric fields across all rows — insufficient data for correlation computation
- row_id empty or exceeds 80 characters — schema rejection
- Payment not fulfilled — x402 payment required before response

## How this service works

Time entries - Two-measure correlation: Two-measure correlation for Time entries. Up to 200 supplied typed records. Local numeric and data-quality processing; no external enrichment or forecasting. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded two-measure correlation deliverable.

## Output

Returns a single bounded two-measure correlation deliverable: the computed correlation coefficient (and likely supporting data-quality metrics) between the 'hours' and 'billable_hours' fields across the submitted time entry rows. No external data is fetched; all processing is local and numeric.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/time-entries-two-measure-correlation-9b052227/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)