# Business Frameworks – Binding Node (Market Supply Chain Tightness) > Business Frameworks – Binding Node (Market Supply Chain Tightness) is a paid API for AI agents from business-frameworks.matryoshka-paradigms.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-17). Identifies the binding (tightest) node in a supply chain path from end demand to upstream limit, computing effective tightness, dominant transmission, and lag at each node deterministically. ## Facts - Endpoint: POST https://business-frameworks.matryoshka-paradigms.workers.dev/apply/market/decide/binding-node?utm_source=zero.xyz - Price: $0.05/call - Payment: x402 - Status: unknown - Last checked: 2026-10-17 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/business-frameworks-binding-node-market-supply-chain-tightness-6243f0f8 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vAiolTXoNbIR2QBqn_VBd 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 business-frameworks-binding-node-market-supply-chain-tightness-6243f0f8 -d '' ``` Example prompt: I have a three-node supply chain — end consumers (tightness 4), specialty chemical producers (tightness 8), and rare mineral miners (tightness 9) — with edge weights of 0.75 and 0.9 and lags of 0 and 6 months respectively; which is the binding node, what's the effective tightness at each stage, and how long before upstream tightening hits consumers? ## When to prefer this Choose this endpoint when you need a deterministic, rule-based identification of which node in a linear supply chain path is the binding constraint — especially when you already have tightness scores (e.g. from the pricing-power endpoint) and edge weights. Prefer it over generic LLM analysis when you need reproducible, auditable verdicts with exact lag estimates. It is specifically designed for ordered chains (not general graphs) and pairs naturally with the sibling shock, verdict, and rent endpoints in the same framework. ## Known failure modes - Missing required 'chain' or 'edges' array returns a schema validation error - Chain has fewer than 2 nodes — rejected with minimum items error - Edge array length does not match chain length minus one — structural mismatch error - Tightness or weight values outside 0–10 / 0–1 bounds return validation failure - driver_share provided without driver_cagr (or vice versa) may produce undefined behavior - Network timeout or worker cold-start can cause 5xx on first call ## How this service works Business Frameworks · business-frameworks/market/decide/binding-node@1.2, applied — POST a chain from end demand to the upstream limit with each node's tightness and each edge's weight and lag; get effective tightness along the path, the binding node, the dominant transmission and the lag to each seat. Deterministic (the node's rule, no model): figures, verdict, action and check with the 256-token node text — schema free at GET /apply/market/decide/binding-node. ## Output Returns the effective tightness score along the path for each node, identifies the single binding (tightest/most constraining) node, specifies the dominant transmission route, gives the lag in months before tightening at each upstream node reaches each downstream seat, and provides a deterministic verdict, recommended action, and a short check text (up to 256 tokens) — all computed by fixed rule with no AI model involved. ## Request schema (JSON Schema) ```json { "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "input" ], "properties": { "input": { "type": "object", "required": [ "type", "method", "bodyType", "body" ], "properties": { "body": { "type": "object", "required": [ "chain", "edges" ], "properties": { "chain": { "type": "array", "items": { "type": "object", "required": [ "id", "tightness" ], "properties": { "id": { "type": "string", "description": "A short label for the node." }, "pull": { "type": "number", "maximum": 10, "minimum": 0, "description": "The node's own demand pull, 0 to 10. Optional; end demand usually carries it. Or send driver_share and driver_cagr and the rule computes it." }, "tightness": { "type": "number", "maximum": 10, "minimum": 0, "description": "The node's own tightness, 0 to 10, from market/decide/pricing-power's T or the caller's score." }, "demand_end": { "type": "boolean", "description": "true marks the demand pool. Optional; the first node is the demand end by default." }, "driver_cagr": { "type": "number", "maximum": 3, "minimum": -0.9, "description": "Optional, with driver_share: the driver slice's three-year growth rate (0.6 means 60% a year)." }, "driver_share": { "type": "number", "maximum": 1, "minimum": 0, "description": "Optional, with driver_cagr: the driver's share of the node's demand." }, "external_constraint": { "type": "number", "maximum": 10, "minimum": 0, "description": "Optional: the largest weighted tightness reaching this node from an input edge off this path." } } }, "minItems": 2, "description": "The path in order from end demand (first) to the upstream limit (last)." }, "edges": { "type": "array", "items": { "type": "object", "required": [ "w" ], "properties": { "w": { "type": "number", "maximum": 1, "minimum": 0, "description": "Non-substitutability of the upstream nod … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/business-frameworks-binding-node-market-supply-chain-tightness-6243f0f8/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from business-frameworks.matryoshka-paradigms.workers.dev](https://www.zero.xyz/host/business-frameworks.matryoshka-paradigms.workers.dev/llms.txt)