# Ceramic Measurements - Reference Integrity Map

> Ceramic Measurements - Reference Integrity Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035197/call, status unknown (last checked 2026-11-04).

Binds ceramic measurement rows to a specific supplied dataset, material lot, and revision, verifying referential integrity against the provided record rather than performing independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ceramic-measurements/reference-integrity-map?utm_source=zero.xyz
- Price: $0.035197/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ceramic-measurements-reference-integrity-map-b27fde0d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m0aDElBA42eqHWmz6j-DX

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 ceramic-measurements-reference-integrity-map-b27fde0d -d '<json body>'
```

Example prompt: Can you check that these ceramic measurement rows (up to 32 rows, public data, nonpersonal metadata) are correctly bound to these specific lot identifiers — I want to confirm the reference integrity before we submit the batch for review.

## When to prefer this

Use this endpoint when you need to verify that ceramic measurement rows are correctly bound to a specific supplied dataset, lot, revision, or content record — especially before archiving, submitting, or auditing a ceramic data batch. Prefer this over provenance or duplicate endpoints when the primary concern is referential binding (row-to-record association) rather than provenance chain integrity or duplicate detection.

## Known failure modes

- Rows array empty or exceeds 32-item limit — validation error
- Lots array empty or exceeds 32-item limit — validation error
- dataClass not one of 'public' or 'synthetic' — schema rejection
- nonpersonalMetadata not explicitly true — request rejected
- Row identifiers do not correspond to any supplied lot — binding failure flagged in output
- Malformed input JSON — parsing error

## How this service works

Bind measurement rows to the exact supplied dataset/material/lot/revision/content Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A reference integrity map indicating which measurement rows are correctly bound to the supplied dataset, material lot, revision, and content identifiers, along with any rows that fail to match the declared record — returned as a supplied-record analysis, not an independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lots": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "rows": {
   "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/ceramic-measurements-reference-integrity-map-b27fde0d/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)