passlisted in Coinbase#48 by calls of 156 on this host
0.15 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-09 10:13 UTC
- First observed by TOLLderived
- 2026-10-09
- Pricederived
- 0.15 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 12 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
micro assembly schedule compare shares www.mahastrategies.com with 155 other listed endpoints and is tied 48th by calls with 108 others.
Callers of micro assembly schedule compare supply a json body with the fields dataClass and scenarios.
A response from micro assembly schedule compare, as declared, includes result, offerId, version, boundaries, inputDigest, receiptDigest and 1 other.
micro assembly schedule compare drew a single call from a single payer in the trailing 30 days.
The last call to micro assembly schedule compare came 4 days before the snapshot, 2026-10-09.
A call to micro assembly schedule compare costs 0.15 USDC on Base, as declared.
micro assembly schedule compare answers POST requests at www.mahastrategies.com; it is listed in the Coinbase registry and TOLL files it under inference.
micro assembly schedule compare answered the sweep of 2026-10-21 with a valid 402, as at every sweep since 2026-10-09.
Closest in price to micro assembly schedule compare within inference: llm pro at agent402.tools and locus practitioner read at api.locus.report.
micro assembly schedule compare is near the top of prices in inference; 98% of comparable listings are cheaper.
The wallet paid by micro assembly schedule compare is the payee of 156 endpoints on one host.
The seller's own tags are bounded-computation, evidence, deterministic and microproduct.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.15 USDC | exact | 0xec84c1…62de28 |
the checks, as of 2026-10-21 20:34 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-21 20:34 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-19 11:03 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 19:09 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-16 08:52 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 10:49 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 08:40 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 13:32 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 10:56 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 09:38 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 17:48 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 13:46 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-09 13:30 UTC | pass | 0 | new-after-daily-2026-10-09 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-09 10:13 UTC · method · live
The input and output block
{
"input": {
"body": {
"dataClass": "synthetic",
"scenarios": [
{
"id": "one-crew",
"crews": 1,
"units": 10,
"liftMs": 240000,
"connectionMs": 300000,
"inspectionMs": 180000,
"factoryIntervalMs": 480000
},
{
"id": "two-crews",
"crews": 2,
"units": 10,
"liftMs": 240000,
"connectionMs": 300000,
"inspectionMs": 180000,
"factoryIntervalMs": 480000
}
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"result": {
"rows": [
{
"id": "one-crew",
"status": "estimated",
"metrics": [
{
"name": "completionMs",
"value": "7200000"
}
],
"relatedIds": []
}
],
"basis": "synthetic",
"method": "assembly-schedule-compare/1",
"totals": [],
"limitations": [
"First unit ready at time zero; later units released at fixed int…"
],
"approvalGranted": false
},
"offerId": "assembly-schedule-compare",
"version": "maha-microproducts/0.1",
"boundaries": [
"Public or synthetic inputs only. Caller labels are declarations,…"
],
"inputDigest": "sha256:6e2832b5e603403130a1b4c1451cc6ced2e17ddcdcdc3610bfb8414c2…",
"receiptDigest": "sha256:3674c1805c6b126a704467b5605eefd25c7747623b10588be10bd6876…",
"amountBaseUnits": "150000"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "micro assembly schedule compare on www.mahastrategies.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/www-mahastrategies-com-api-v1-micro-assembly-schedule-compare-bd841b/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-www-mahastrategies-com-api-v1-micro-assembly-schedule-compare-bd841b-2026-10-13T14-08Z,
author = {TOLL},
title = {micro assembly schedule compare on www.mahastrategies.com},
howpublished = {\url{https://tollindex.com/e/www-mahastrategies-com-api-v1-micro-assembly-schedule-compare-bd841b/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.