# Ceramic Measurements - Scope Boundary Audit

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

Validates that ceramic lot/method-pinned measurement records conform to declared owner, subject, revision, and allowed scope labels, flagging any scope boundary violations.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ceramic-measurements/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038321/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-scope-boundary-audit-0ed144ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E-eIQRQefiA57ng4HsWgz

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-scope-boundary-audit-0ed144ed -d '<json body>'
```

Example prompt: Audit these 12 ceramic lot measurement rows for scope boundary compliance — the owner ref is 'maha-lab-01', subject ref is 'ceramic-batch-7', revision is 'v2.3', allowed scopes are ['internal','research'], and the data class is 'synthetic' with nonpersonal metadata confirmed.

## When to prefer this

Choose this endpoint when you need to enforce strict scope boundary compliance on ceramic lot or method-pinned measurement records against a declared owner/subject/revision/scope frame. It is specifically designed for ceramic measurement data governance and scope-label auditing, not general-purpose data validation or certification. Prefer it over generic validators when working with ceramic materials records that require pin-level scope enforcement.

## Known failure modes

- Missing required fields (ownerRef, subjectRef, revision, allowedScopes) return validation errors
- Rows array exceeding 32 items or below 1 item is rejected
- nonpersonalMetadata must be explicitly true (const); any other value fails
- dataClass must be exactly 'public' or 'synthetic'; other values rejected
- Malformed or unrecognized scope labels may produce inconclusive audit results
- Service may return error if revision string format is unrecognized

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for ceramic lot/method-pinned measurement Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit report indicating whether each submitted ceramic measurement row complies with the declared owner, subject, revision, and allowed scope labels. Highlights any rows where scope labels grant no valid permission or where pin mismatches are detected. Does not certify the measurements independently — results reflect supplied-record analysis only.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "ownerRef": {
   "type": "string"
  },
  "revision": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "subjectRef": {
   "type": "string"
  },
  "allowedScopes": {
   "type": "array",
   "maxItems": 16,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ceramic-measurements-scope-boundary-audit-0ed144ed/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)