# Thermal Measurements Provenance Edge Audit

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

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

## Facts

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

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

Example prompt: Audit the provenance edges for these 10 thermal measurement rows using public data class — I need to confirm they're correctly bound to the declared dataset, material lot, method, and source-revision manifests.

## When to prefer this

Use this endpoint when you need to audit provenance edges specifically for thermal measurement data and require binding rows to exact source-revision and content manifests. Prefer this over generic data validation services when the domain is thermal/materials science measurements and you need manifest-level pinning rather than schema-level validation. Distinct from polymer, ceramic, or catalyst measurement provenance endpoints which target different material types.

## Known failure modes

- Row count exceeds 32-item maximum — request rejected
- Sources array empty or exceeds 32 items — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not explicitly true — request rejected
- Manifest hash mismatch — binding fails but no error thrown, audit result reflects mismatch
- Malformed row structure — parsing error returned

## 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 showing whether each measurement row is correctly bound to its declared dataset, material, lot, method, source-revision, and content manifests. Indicates which pins match or fail, but does not certify experimental results independently — this is a supplied-record analysis only.

## 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/thermal-measurements-provenance-edge-audit-ef94e665/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)