# Optical Measurements Provenance Edge Audit

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

Binds optical measurement rows to exact dataset, material, lot, method, source-revision, and content manifests to audit provenance edges for supplied records.

## Facts

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

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 optical-measurements-provenance-edge-audit-a9ef79e4 -d '<json body>'
```

Example prompt: Audit the provenance edges on these 5 optical measurement rows against their declared dataset, material lot, method, and source-revision manifests — data class is 'synthetic' and all metadata is non-personal.

## When to prefer this

Use this endpoint when you need to programmatically audit whether optical measurement records are correctly associated with their declared provenance metadata — specifically dataset, material lot, method, source-revision, and content manifests. Prefer it over generic data-validation endpoints when the domain is optical measurements and the goal is traceability/lineage verification rather than statistical analysis or format conversion. Not suitable if you need independent experimental certification or live instrument data.

## Known failure modes

- Row count exceeds 32-item maximum, causing validation rejection
- Source array is empty or exceeds 32 items
- dataClass not set to 'public' or 'synthetic' — unsupported enum value
- nonpersonalMetadata not explicitly set to true — required constant
- Manifest or source-revision references do not match any supplied row, resulting in unbound edge flags
- Malformed row objects missing required measurement fields

## How this service works

Bind measurement rows to exact dataset/material/lot/method/source-revision/content manifests; matching pins do not prove experimental Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns audit results indicating whether each measurement row's provenance edges are correctly bound to the declared dataset, material, lot, method, source-revision, and content manifests. Flags any mismatches or unmatched pins. Does not provide independent experimental certification — analysis is based entirely on the supplied records.

## 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/optical-measurements-provenance-edge-audit-a9ef79e4/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)