# Assembly Critical Path Analyzer

> Assembly Critical Path Analyzer is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.100006/call, status unknown (last checked 2026-10-16).

Computes earliest/latest start and finish times, total slack, and peak resource overlap for a DAG of up to 48 manufacturing tasks using critical path method (CPM).

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/manufacturing/critical-path?utm_source=zero.xyz
- Price: $0.100006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/assembly-critical-path-analyzer-26713524
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0Fic7vmzZ4n-qT0wwuc74

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 assembly-critical-path-analyzer-26713524 -d '<json body>'
```

Example prompt: Calculate the critical path for my assembly process — I have 12 tasks with dependencies and unit resource claims, all labeled as synthetic data. Tell me the earliest and latest starts, finishes, slack for each task, and peak resource overlap at the earliest schedule.

## When to prefer this

Use this endpoint when you need fast, deterministic critical path method (CPM) analysis on a small-to-medium task DAG (up to 48 tasks) in a manufacturing or assembly context, and you want cycle detection, slack computation, and peak resource overlap reporting in a single call. It is not a resource-constrained scheduler or optimizer — choose it for analytical CPM output, not for solving resource-leveling or job-shop scheduling problems.

## Known failure modes

- Cycle detected in DAG — endpoint rejects input and returns an error identifying the circular dependency
- Unknown dependency reference — a task references a task ID not present in the task list, triggering rejection
- Task count exceeds 48 — input validation error
- Resource array exceeds 16 entries — input validation error
- Invalid dataClass value — must be 'public' or 'synthetic'
- Payment failure — x402 payment not completed, request rejected

## How this service works

Compute earliest/latest starts and finishes and slack on a declared DAG of at most 48 tasks. Rejects cycles and unknown dependencies. Reports peak overlap of declared unit resource claims at the earliest schedule; does not optimize a resource-constrained schedule or verify physical resources. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns earliest and latest start/finish times and total slack for each task, identifies the critical path (zero-slack chain), reports peak simultaneous resource overlap at the earliest schedule, and rejects input if cycles or unknown dependency references are detected. Results are retained for 24 hours; receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tasks": {
   "type": "array",
   "maxItems": 48,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "resources": {
   "type": "array",
   "maxItems": 16,
   "minItems": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/assembly-critical-path-analyzer-26713524/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)