# Business Frameworks Market Verdict Node > Business Frameworks Market Verdict Node 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). Applies a deterministic supply-chain node rule to classify a market node as binding, transient, pass-through, or open based on capacity and pricing inputs ## Facts - Endpoint: POST https://business-frameworks.matryoshka-paradigms.workers.dev/apply/market/decide/verdict?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-market-verdict-node-a219a532 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lf5r1CC3r9JRz3SW5EGzP 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-market-verdict-node-a219a532 -d '' ``` Example prompt: For our semiconductor fab node, the supply is short inside the 36-month horizon, lead time is 24 months, suppliers are actively building (with dated announcements), no relief is documented inside the horizon, and price is not set by a wider commodity cycle — supply is not elastic. What verdict does the binding-node rule give us? ## When to prefer this Use this endpoint when you need a fast, deterministic, rule-based classification of a single supply-chain node's market position — no LLM inference, no probabilistic scoring. Prefer it over general-purpose AI analysis when auditability and reproducibility matter, or when you are running the node verdict as one step in a larger supply-chain pipeline (e.g. after the binding-node endpoint). Not suitable for portfolio-level analysis or qualitative narrative generation. ## Known failure modes - Missing required boolean or integer fields returns a validation error - lead_time_months or horizon_months below minimum (0 or 1 respectively) rejected - Inconsistent combinations (e.g. relief_documented_inside_horizon true when short_inside_horizon false) may produce unexpected but valid verdicts - Payment not included or invalid x402 token returns 402 Payment Required - Schema mismatch on the nested input.body structure causes rejection ## How this service works Business Frameworks · business-frameworks/market/decide/verdict@1.2, applied — POST whether the node is short inside the horizon, lead time and horizon, whether suppliers are building, documented relief and how the price is set; get the node's verdict — binding, transient, pass-through or open — and the fact that decided it. Deterministic (the node's rule, no model): figures, verdict, action and check with the 234-token node text — schema free at GET /apply/market/decide/verdict. ## Output Returns the node's verdict label (binding, transient, pass-through, or open), the specific fact that triggered the verdict under the deterministic rule, an action recommendation, and a check summary — all accompanied by the 234-token node rule text. No model inference; output is fully rule-determined from the inputs. ## 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": [ "short_inside_horizon", "lead_time_months", "horizon_months", "suppliers_building", "relief_documented_inside_horizon", "price_set_by_wider_cycle", "supply_elastic" ], "properties": { "horizon_months": { "type": "integer", "minimum": 1, "description": "The planning horizon in months. The product's default horizon is three years (36)." }, "supply_elastic": { "type": "boolean", "description": "true if supply can be added inside the lead time by many sellers at ordinary cost." }, "lead_time_months": { "type": "integer", "minimum": 0, "description": "Months from a decision to add capacity to that capacity producing, for this node, from suppliers' own statements." }, "suppliers_building": { "type": "boolean", "description": "true if the node's supplier set is adding capacity now, on filings or announcements with a date." }, "short_inside_horizon": { "type": "boolean", "description": "true if the node's capacity cannot meet its demand at some point inside the horizon, on documented forecasts. The caller's judgment of the evidence." }, "price_set_by_wider_cycle": { "type": "boolean", "description": "true if the node's price is set by a market wider than this chain — a global commodity, a rate — so its own tightness does not price." }, "relief_documented_inside_horizon": { "type": "boolean", "description": "true only for named capacity with a start date inside the horizon; an announcement without a date is false." } }, "description": "Shares and weights are fractions from 0 to 1 (0.65 means 65%). Scores run 0 to 10. Force scores are whole numbers 1 to 5, scored as pressure on the seller's margins (1 weak, 5 strong). Months are whole numbers. Years are calendar years for crossing and base, and a count for the horizon." }, "type": { "type": "string", "const": "http" }, "method": { "enum": [ "POST" ], "type": "string" }, "bodyType": { "enum": [ … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/business-frameworks-market-verdict-node-a219a532/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)