# Edition Records - Scope Boundary Audit

> Edition Records - Scope Boundary Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.038341/call, status unknown (last checked 2026-10-25).

Validates that edition record rows conform to declared owner, subject, revision, and allowed scope labels, flagging any mismatches or unauthorized scope claims.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/edition-records/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038341/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/edition-records-scope-boundary-audit-fed2af9f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dhzIxLyVnOJVzMWtqq159

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 edition-records-scope-boundary-audit-fed2af9f -d '<json body>'
```

Example prompt: Audit these 12 edition record rows against owner ref 'pub-001', subject ref 'work-447', revision 'r3', and allowed scopes ['internal','review'] with data class 'public' and confirm no records fall outside the declared scope boundary.

## When to prefer this

Use this endpoint when you need to deterministically validate whether a batch of edition records stays within explicitly declared scope boundaries (owner, subject, revision, allowed scope labels) without requiring independent certification. Prefer it over general-purpose schema validators when the records are library/publishing edition records with structured scope label semantics, and when you need a record-level audit trail rather than a document-level diff.

## Known failure modes

- Rows array empty or exceeds 32 items — request rejected
- allowedScopes array empty or exceeds 16 items — validation error
- Missing required ownerRef or subjectRef — malformed request error
- nonpersonalMetadata not set to true — schema const violation
- dataClass not one of 'public' or 'synthetic' — enum validation error
- Malformed revision string — unparseable revision error
- Payment of 0.038341 USDC not fulfilled — 402 Payment Required

## How this service works

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

## Output

Returns a structured audit report indicating which edition record rows conform to or violate the declared owner, subject, revision, and allowed scope constraints. Includes per-row findings, label match status, and an overall boundary compliance assessment. Does not certify permissions independently — results are based on 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/edition-records-scope-boundary-audit-fed2af9f/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)