# Alloy Measurements Provenance Edge Audit

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

Binds alloy measurement rows to their exact dataset, material, lot, method, source-revision, and content manifests to establish data provenance chains for supplied records.

## Facts

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

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 alloy-measurements-provenance-edge-audit-370957c6 -d '<json body>'
```

Example prompt: Audit the provenance of these 12 alloy measurement rows against their declared sources — the data class is synthetic and I can confirm there's no personal metadata — and tell me which dataset/lot/method/source-revision manifests each row binds to.

## When to prefer this

Use this endpoint when you need to establish or audit data provenance for alloy measurement records against known source manifests, especially for synthetic or public datasets where tracing back to exact dataset versions, lots, and methods is required. Prefer this over generic data lineage tools when working specifically with alloy or materials measurement data and needing row-level binding to source-revision manifests.

## Known failure modes

- rows array empty or exceeds 32 items — request rejected
- sources array empty or exceeds 32 items — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not explicitly true — request rejected
- no matching source-revision or manifest found for a row — partial or empty binding result
- malformed row or source objects — schema validation error

## 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 provenance binding results that link each supplied measurement row to its matched dataset, material, lot, method, source-revision, and content manifest identifiers. Results indicate which pins matched but explicitly do not constitute independent certification or proof of experimental validity.

## 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/alloy-measurements-provenance-edge-audit-370957c6/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)