# Token Buy Receipt Shortfall — Named Scenario Comparison

> Token Buy Receipt Shortfall — Named Scenario Comparison is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Compares named scenarios of token buy receipt shortfall (expected vs actual tokens received) against a baseline, returning a deterministic verdict for each scenario.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-bx-token-buy-receipt-scenario?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/token-buy-receipt-shortfall-named-scenario-comparison-2edccb93
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qQtTE4LBfyRDq9nH_FjQI

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 token-buy-receipt-shortfall-named-scenario-comparison-2edccb93 -d '<json body>'
```

Example prompt: Compare my token buy shortfall where the baseline is 950 actual tokens out of 1000 expected, and run two named scenarios: 'Higher expectation' with 1100 expected tokens and 'Lower expectation' with 900 expected tokens, so I can see the shortfall differences side by side.

## When to prefer this

Choose this endpoint when you need a deterministic, multi-scenario comparison of token buy receipt shortfall using caller-supplied token counts — specifically when you want to label and compare named what-if cases (e.g. 'Contract A vs Contract B') against a common baseline. Prefer it over a single-calculation endpoint when you need side-by-side scenario verdicts in one call. This is not appropriate for live market scanning, real-time price feeds, or trade signal generation.

## Known failure modes

- Missing or zero expected_tokens in baseline causes validation failure
- Scenario overrides object with no properties (minProperties:1 not met) returns schema error
- More than 20 scenarios supplied exceeds maxItems limit
- Label field empty or exceeding 80 characters causes rejection
- Negative actual_tokens value violates minimum:0 constraint
- Network or payment authorization failure returns 402 or payment error

## How this service works

Token buy receipt shortfall — Named scenario comparison: Named scenario comparison for Token buy receipt shortfall. Supplied token observations only. Deterministic calculation or caller-threshold verdict, not a live scan, safety proof or trade recommendation. Specialised preset in a shared 50-profile, 20-operation engine. 0.01 USDC includes one bounded named scenario comparison report.

## Output

Returns a named scenario comparison report containing, for each labeled scenario, the computed token shortfall (difference between expected and actual tokens) relative to the baseline inputs, along with a deterministic verdict. The report is bounded to the supplied observations and does not perform live market scanning or provide trade recommendations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "baseline": {
   "type": "object",
   "default": {
    "actual_tokens": 950,
    "expected_tokens": 1000
   },
   "required": [
    "expected_tokens",
    "actual_tokens"
   ],
   "properties": {
    "actual_tokens": {
     "type": "number",
     "default": 950,
     "maximum": 10000000000000000,
     "minimum": 0
    },
    "expected_tokens": {
     "type": "number",
     "default": 1000,
     "maximum": 10000000000000000,
     "minimum": 0,
     "exclusiveMinimum": 0
    }
   },
   "additionalProperties": false
  },
  "scenarios": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "label",
     "overrides"
    ],
    "properties": {
     "label": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "overrides": {
      "type": "object",
      "properties": {
       "actual_tokens": {
        "type": "number",
        "default": 950,
        "maximum": 10000000000000000,
        "minimum": 0
       },
       "expected_tokens": {
        "type": "number",
        "default": 1000,
        "maximum": 10000000000000000,
        "minimum": 0,
        "exclusiveMinimum": 0
       }
      },
      "minProperties": 1,
      "additionalProperties": false
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "label": "Supplied alternative",
     "overrides": {
      "expected_tokens": 1100
     }
    }
   ],
   "maxItems": 20,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/token-buy-receipt-shortfall-named-scenario-comparison-2edccb93/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)