# Business Frameworks – Market Shock Pass-Through Verdict (market/decide/shock@1.2) > Business Frameworks – Market Shock Pass-Through Verdict (market/decide/shock@1.2) 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 shock rule to produce a verdict on whether a market node can pass through a given shock, including step count, lag, and a transfer test. ## Facts - Endpoint: POST https://business-frameworks.matryoshka-paradigms.workers.dev/apply/market/decide/shock?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-shock-pass-through-verdict-market-decide-6232af81 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vYdh2gMYCSOQX1hCMyoNP 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-shock-pass-through-verdict-market-decide-6232af81 -d '' ``` Example prompt: Run the shock pass-through verdict for my supply chain node: it's a type A end-demand collapse shock, the marginal buyer mix is 60% tier 1 and 40% tier 2, propensity is 'rent', driver share is 0.7, lead time is 6 months, and I'm looking at a 24-month horizon — tell me the verdict steps, lag, and whether it passes the transfer test. ## When to prefer this Choose this endpoint when you need a deterministic, rule-based verdict on shock pass-through for a specific supply-chain market node — particularly when you have structured inputs for buyer tier mix, propensity, driver share, and lead time. Prefer this over general LLM reasoning when you need a reproducible, schema-consistent verdict with an explicit transfer test and lag estimate rather than a probabilistic narrative answer. ## Known failure modes - Missing required fields (shock_type, tier_mix_marginal, propensity_read, driver_share, lead_time_months, horizon_months) returns a validation error - Invalid shock_type enum value (not A/B/C/D) returns a schema error - Invalid propensity_read value (not rent/ceded/mixed) returns a schema error - driver_share outside [0,1] range returns a validation error - Analog provided with mismatched tier_mix shape causes transfer test to be skipped or flagged - Payment not included or insufficient USDC returns 402 Payment Required ## How this service works Business Frameworks · business-frameworks/market/decide/shock@1.2, applied — POST the shock type, the node's marginal buyer tiers, the propensity read, the driver share, lead time and horizon, and an analog if one exists; get the verdict steps and the lag that reach the seat, with the transfer test applied. Deterministic (the node's rule, no model): figures, verdict, action and check with the 298-token node text — schema free at GET /apply/market/decide/shock. ## Output Returns the number of verdict steps toward pass-through the node can achieve, the estimated lag in months before the shock reaches the seat, the result of the transfer test (pass/fail), a recommended action, a check condition, and the 298-token node rule text explaining the deterministic logic applied. ## 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": [ "shock_type", "tier_mix_marginal", "propensity_read", "driver_share", "lead_time_months", "horizon_months" ], "properties": { "analog": { "type": "object", "required": [ "verdict_steps", "tier_mix" ], "properties": { "tier_mix": { "type": "object", "properties": { "t1": { "type": "number" }, "t2": { "type": "number" }, "t3": { "type": "number" }, "t4": { "type": "number" } }, "description": "The buyer tiers of that shock's marginal demand, same shape as tier_mix_marginal." }, "lag_months": { "type": "integer", "minimum": 0, "description": "Months from that shock to the move. Optional; default 0." }, "verdict_steps": { "type": "integer", "minimum": 0, "description": "How many verdict steps toward pass-through the node moved in the historical shock the caller names." } }, "description": "Optional: a historical shock to carry, if its buyer tiers match today's." }, "shock_type": { "enum": [ "A", "B", "C", "D" ], "type": "string", "description": "A: end demand collapses. B: suppliers overbuild in a capacity race. C: credit to tier 3 and 4 buyers tightens. D: policy — export or materials controls, interconnection rules, priority orders." }, "driver_share": { "type": "number", "maximum": 1, "minimum": 0, "description": "Share of the node's demand that comes from the chain's demand driver." }, "horizon_months": { "type": "integer", "minimum": 1, "description": "The planning horizon in months." }, "dispersion_flag": { "type": "boolean", "description": "true if the node's entities are expected to fare very differently in the shock although the market-level magnitude is one number. Optional; default false." }, "prope … (truncated) ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/business-frameworks-market-shock-pass-through-verdict-market-decide-6232af81/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)