Back to Browse
Multilevel BOM MRP Netting with Lot-Multiple and Lead-Time Offset
x402
Multilevel BOM MRP Netting with Lot-Multiple and Lead-Time Offset is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-04).
Computes bounded multilevel bill-of-materials (BOM) integer piece-count plans using MRP netting logic, applying lot-multiple rounding and lead-time offsets to expose past-due and future planned orders.
Price / call$0.003
Success—
StatusUnknown
How this service works
Compute bounded multilevel integer piece-count plans and explicitly expose past-due needs.
Output
Returns a structured period-by-period MRP plan for each item in the BOM including net requirements, planned order receipts (rounded to lot multiples), planned order releases offset by lead time, and flagged past-due requirements where lead-time offset pushes orders into or before period zero. Output is bounded at 20,000 bytes; oversized results return an error without charge.
Example use cases
Weekly production order plan for a finished assembly
“I need to plan production orders for the next 8 periods for assembly SKU-500, which has 200 units on hand, a safety stock of 50, a lead time of 3 periods, and a lot multiple of 100. Demand is [150, 200, 180, 220, 170, 190, 210, 160] with no scheduled receipts. It has two sub-components: SUB-A (qty 3 each) and SUB-B (qty 1 each) — both with their own stock and lead times. Can you compute the full multilevel MRP plan and show me where past-due needs appear?”
Identify past-due purchase orders for a purchased component
“We have a purchased part PART-X with 0 units on hand, safety stock of 25, lead time of 4 periods, and a lot multiple of 50. Demand driven from our parent assembly is [75, 75, 75, 75] over 4 periods with no scheduled receipts. Run the MRP netting and tell me which orders are past due given the lead time offset.”
Lot-size rounding impact on a two-level BOM
“Can you compute the multilevel MRP plan for 6 periods for item WIDGET-TOP (on-hand 30, safety stock 5, lead time 1, lot multiple 200, demand [50,60,70,80,90,100], scheduled receipts [0,100,0,0,0,0]) and its child WIDGET-BASE (quantity 4, on-hand 500, safety stock 100, lead time 2, lot multiple 500, demand [0,0,0,0,0,0], scheduled [0,0,0,0,0,0])? I want to see how the lot-multiple rounding cascades down to the component level.”
Technical details
Endpoint
POSThttps://detect.halowerk.com/v1/F-TD2000-ENGINEERING-B001/multilevel-bom-lot-multiple-netting-lead-time-offset?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need deterministic, bounded integer MRP netting across a multilevel bill of materials with explicit lot-multiple rounding and lead-time period offsets — particularly when you need to surface past-due requirements. Prefer this over generic planning tools when your BOM has up to 16 items, up to 24 planning periods, and you need reproducible integer arithmetic rather than heuristic or approximate planning.
Side effects
- Input exceeds 16,000 UTF-8 bytes — returns error without charge
- Computed result exceeds 20,000 bytes — returns error without charge
- Invalid BOM structure (e.g. missing required fields, out-of-range integers) — schema validation error
- Circular BOM references or item ID mismatches between children and items list
- Demand or scheduled arrays length mismatch with periods count
- lot_multiple of zero (minimum is 1) — rejected at schema validation
- Payment claim missing or invalid — x402 payment required error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| artifact | object | Bounded model; oversized UTF-8 input (16000 bytes) or computed result (20000 bytes) returns unknown without truncation or charge. |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"