# Reaction Records Provenance Edge Audit

> Reaction Records Provenance Edge Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.045316/call, status unknown (last checked 2026-10-16).

Binds reaction records to exact dataset, method, source-revision, and content manifest pins for provenance tracing — not independent certification or experimental verification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045316/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reaction-records-provenance-edge-audit-329fa440
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IC9LMRTEJUML9GA3y9Zx4

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 reaction-records-provenance-edge-audit-329fa440 -d '<json body>'
```

Example prompt: Bind these 5 reaction record rows to their dataset and method source-revision pins — the data class is 'synthetic' and all metadata is non-personal; I need a provenance edge audit to confirm the manifest linkage.

## When to prefer this

Choose this endpoint when you need to formally bind reaction record rows to exact source-revision and content manifest pins for provenance tracing, particularly for synthetic or public datasets where nonpersonal metadata compliance is required. Prefer this over general data validation endpoints when the specific domain is reaction records and the goal is provenance edge auditing rather than independent experimental certification.

## Known failure modes

- Rows array empty or exceeds 32-item limit — validation error returned
- Sources array empty or exceeds 32-item limit — validation error returned
- Invalid or missing dataClass enum value (must be 'public' or 'synthetic') — schema rejection
- nonpersonalMetadata not set to true — const constraint violation
- Payment not provided or insufficient — x402 payment required response
- Malformed row or source objects — parsing error

## How this service works

Bind reaction records to exact dataset/method/source-revision/content manifest pins; no proof of real experimental execution or causal Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured provenance binding result confirming how each submitted reaction record row is pinned to the declared dataset, method, source-revision, and content manifest identifiers. Does not independently verify experimental execution or certify causal analysis — only confirms the declared linkage structure.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reaction-records-provenance-edge-audit-329fa440/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)