Manufacturing Schedule Comparison
by Assembly Schedule Comparison in Other
Simulate up to 10 sequential assembly scenarios of 100 identical units using one shared crane and declared crews. Factory releases, lift and connection durations are explicit. No lift-capacity, structural, site-safety or optimized scheduling approval. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.
https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison- Price
- $0.15
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 178 ms
- 2.8 s slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison
Each call costs $0.150001 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison
content-type: application/json
{
"dataClass": "synthetic",
"scenarios": [
{
"connectionMs": 300000,
"crews": 1,
"factoryIntervalMs": 480000,
"id": "one-crew",
"inspectionMs": 180000,
"liftMs": 240000,
"units": 10
},
{
"connectionMs": 300000,
"crews": 2,
"factoryIntervalMs": 480000,
"id": "two-crews",
"inspectionMs": 180000,
"liftMs": 240000,
"units": 10
}
]
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dataClass | string | Yes | One of: public, synthetic. |
scenarios | array | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 39 lines
{
"data": {
"chargedAmount": "150001",
"inputHash": "sha256:6e2832b5e603403130a1b4c1451cc6ced2e17ddcdcdc3610bfb8414c2…",
"limitations": [
"Public or synthetic inputs only. Caller labels are declarations,…"
],
"productId": "assembly-schedule-compare",
"result": {
"approvalGranted": false,
"basis": "synthetic",
"limitations": [
"First unit ready at time zero; later units released at fixed int…"
],
"method": "assembly-schedule-compare/1",
"rows": [
{
"id": "one-crew",
"metrics": [
{
"name": "completionMs",
"value": "7200000"
}
],
"relatedIds": [],
"status": "estimated"
}
],
"totals": []
},
"resultHash": "sha256:51a55ff2a02ee7b7b593552024c456a08de46a5279fba2077ea3872a1…",
"sourceContractAmount": "150000",
"version": "maha-legacy-adapter/1"
},
"proof": {
"settlement_id": "0x00000000000000000000000000000000000000000000000000000000000000…"
},
"success": true
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.150001.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","scenarios":[{"connectionMs":300000,"crews":1,"factoryIntervalMs":480000,"id":"one-crew","inspectionMs":180000,"liftMs":240000,"units":10},{"connectionMs":300000,"crews":2,"factoryIntervalMs":480000,"id":"two-crews","inspectionMs":180000,"liftMs":240000,"units":10}]}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","scenarios":[{"connectionMs":300000,"crews":1,"factoryIntervalMs":480000,"id":"one-crew","inspectionMs":180000,"liftMs":240000,"units":10},{"connectionMs":300000,"crews":2,"factoryIntervalMs":480000,"id":"two-crews","inspectionMs":180000,"liftMs":240000,"units":10}]}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.150001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.150001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.150001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fcompute%2Fmanufacturing%2Fschedule-comparison&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dataClass": "synthetic",
"scenarios": [
{
"connectionMs": 300000,
"crews": 1,
"factoryIntervalMs": 480000,
"id": "one-crew",
"inspectionMs": 180000,
"liftMs": 240000,
"units": 10
},
{
"connectionMs": 300000,
"crews": 2,
"factoryIntervalMs": 480000,
"id": "two-crews",
"inspectionMs": 180000,
"liftMs": 240000,
"units": 10
}
]
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.150001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.150001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://www.mahastrategies.com/api/v1/compute/manufacturing/schedule-comparison",
json={
"dataClass": "synthetic",
"scenarios": [
{
"connectionMs": 300000,
"crews": 1,
"factoryIntervalMs": 480000,
"id": "one-crew",
"inspectionMs": 180000,
"liftMs": 240000,
"units": 10,
},
{
"connectionMs": 300000,
"crews": 2,
"factoryIntervalMs": 480000,
"id": "two-crews",
"inspectionMs": 180000,
"liftMs": 240000,
"units": 10,
},
],
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 642 ms | $0.15 |
| 8 h ago | Passed | 402 | 173 ms | $0.15 |
| 13 h ago | Passed | 402 | 2.8 s | $0.15 |
| 18 h ago | Passed | 402 | 168 ms | $0.15 |
| 22 h ago | Passed | 402 | 184 ms | $0.15 |
Show 1 older checks
| 27 h ago | Passed | 402 | 178 ms | $0.15 |