# Spectrometry Records - Provenance Edge Audit

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

Binds spectrum export rows to exact instrument, calibration, acquisition-method, source-revision, and artifact pins for provenance auditing.

## Facts

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

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 spectrometry-records-provenance-edge-audit-687879d0 -d '<json body>'
```

Example prompt: Audit the provenance of these 10 spectrometry export rows against their declared sources — data class is synthetic, non-personal metadata only — and bind each row to its exact instrument, calibration, acquisition method, source revision, and artifact pins.

## When to prefer this

Choose this endpoint when you need to formally bind spectrometry export records to their exact instrument, calibration, and source-revision metadata for provenance tracing — particularly for synthetic or public-class scientific data. Prefer it over generic metadata validators when the specific domain is spectral/instrument science and when pin-level traceability across acquisition methods and artifact revisions is required. Not suitable as independent instrument 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
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true — const validation failure
- Incomplete or malformed row data causing binding failure for individual records
- Source revision pins not resolvable — unmatched provenance returned for affected rows

## How this service works

Bind spectrum exports to exact instrument/calibration/acquisition-method/source-revision/artifact pins; metadata provenance is not proof of instrument Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns provenance binding records that map each input spectrum export row to its exact instrument, calibration revision, acquisition method, source revision, and artifact pins. Results confirm which pins were successfully bound and flag any mismatches or missing provenance links. Does not serve as independent certification — only records the metadata provenance of supplied data.

## 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/spectrometry-records-provenance-edge-audit-687879d0/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)