# Research Correction Propagation

> Research Correction Propagation is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.01007/call, status unknown (last checked 2026-10-26).

Identifies which supplied assay references remain pinned to a corrected (superseded) metadata revision, classifying stale links without asserting truth or efficacy.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/biology/correction-propagation?utm_source=zero.xyz
- Price: $0.01007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/research-correction-propagation-bc9dfecb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HLbee_EKEr3b5JKw9fd5S

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 research-correction-propagation-bc9dfecb -d '<json body>'
```

Example prompt: Check which of these assay references are still pinned to revision v1.0 instead of the corrected revision v1.1 — the data class is public and the sourceId is 'BIO-ASSAY-2024-009'. Supply these 5 reference IDs: [ref-001, ref-002, ref-003, ref-004, ref-005].

## When to prefer this

Use this endpoint when you need to programmatically audit whether a set of assay references have caught up to a known metadata correction, particularly in offline typed-metadata workflows. Prefer this over manual literature review or generic link checkers when working with structured assay bibliographies and versioned revision identifiers. It is purpose-built for biology/assay correction propagation classification, not general citation validation or live document retrieval.

## Known failure modes

- Invalid or missing sourceId returns a validation error
- References array empty or exceeding 32 items triggers a schema rejection
- dataClass not set to 'public' or 'synthetic' causes enum validation failure
- nonpersonalMetadata not set to true (const) causes request rejection
- Unrecognized originalRevision or correctedRevision identifiers may return no matches
- Results unavailable after the 24-hour retention window

## How this service works

Find supplied assay references still pinned to a corrected metadata revision. Classifies links only; does not establish truth, efficacy or source acceptance. Offline typed metadata only. Retained-result recovery: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a classification report indicating which of the supplied assay references are still pinned to the original (pre-correction) metadata revision versus which have propagated to the corrected revision. Does not establish truth, efficacy, or source acceptance — purely classifies link state. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sourceId": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "references": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "originalRevision": {
   "type": "string"
  },
  "correctedRevision": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/research-correction-propagation-bc9dfecb/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)