# Quantum Shot Dataset Lineage Checker

> Quantum Shot Dataset Lineage Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010071/call, status unknown (last checked 2026-10-23).

Validates declared parent IDs, configuration pins, and shot-count totals for quantum shot datasets, detecting missing or cyclic lineage offline without querying hardware.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/quantum/shot-lineage?utm_source=zero.xyz
- Price: $0.010071/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantum-shot-dataset-lineage-checker-b01fdf19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SMS8HXPjrQYcQ2dH_LX8T

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 quantum-shot-dataset-lineage-checker-b01fdf19 -d '<json body>'
```

Example prompt: Check the lineage of these 5 synthetic quantum shot datasets — expected shot count is 10000 and the configuration digest is 'abc123def456' — and tell me if there are any missing or cyclic parent IDs.

## When to prefer this

Choose this endpoint when you need a fast, offline, hardware-independent check of quantum shot dataset lineage metadata — specifically to detect missing or cyclic parent ID chains, validate configuration digest pins, and confirm shot-count totals without executing any quantum hardware queries or randomness validation. Ideal for data quality control pipelines, pre-publication audits, and automated QA workflows on batches of up to 32 synthetic or public quantum datasets.

## Known failure modes

- Invalid or malformed dataset entries return validation errors
- dataClass value outside 'public' or 'synthetic' enum rejected
- nonpersonalMetadata not set to true causes request rejection
- expectedShots outside 0–1,000,000 range returns schema error
- More than 32 datasets in a single request exceeds maxItems limit
- Malformed expectedConfigurationDigest string may produce inconclusive digest comparison
- No result recovery after 24-hour retention window; only minimal receipt metadata available for 90 days

## How this service works

Check declared shot-dataset parent IDs, configuration pins and shot-count totals. Reports missing/cyclic lineage without querying hardware or validating randomness. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured report indicating whether each submitted quantum shot dataset has valid lineage, including flags for missing parent IDs, detected cyclic references, shot-count mismatches against the expected total, and configuration digest pin status — all derived from offline typed metadata without hardware queries.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "datasets": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "expectedShots": {
   "type": "integer",
   "maximum": 1000000,
   "minimum": 0
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "expectedConfigurationDigest": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantum-shot-dataset-lineage-checker-b01fdf19/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)