# Reading Plans Scope Boundary Audit

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

Validates that declared owner, subject, revision, and allowed scope labels in reading plan records match exactly, reporting any scope boundary violations without granting permissions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.03834/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-scope-boundary-audit-abf92502
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7c0cELwWNQ29GH_tuJquU

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 reading-plans-scope-boundary-audit-abf92502 -d '<json body>'
```

Example prompt: Audit these 5 reading plan rows for scope boundary compliance — the owner is 'lib-org-42', subject is 'reader-sub-7', revision is 'v2.1', and the allowed scopes are ['public-read', 'catalog-view']; data class is public and nonpersonal metadata is true.

## When to prefer this

Use this endpoint when you need to audit reading plan metadata records for exact scope boundary compliance — specifically when you have declared owner, subject, revision, and allowed scope labels and need to check for mismatches. Prefer this over generic metadata validators when working within library plan, work, edition, or revision-pinned reading contexts. Not suitable for granting or revoking permissions, independent certification, or raw content access control enforcement.

## Known failure modes

- Rows array empty or exceeds 32 items — validation error
- allowedScopes array exceeds 16 items — request rejected
- nonpersonalMetadata not set to true — required field constraint failure
- dataClass not one of 'public' or 'synthetic' — enum validation error
- Missing required ownerRef, subjectRef, or revision fields — incomplete request error
- Malformed row data causing parse failure — processing error

## How this service works

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

## Output

Returns an audit report identifying which rows have scope boundary violations, listing mismatched owner, subject, revision, or scope label declarations. Does not grant permissions or certify compliance — it analyzes supplied records only and flags discrepancies between declared pins and allowed scope labels.

## 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/reading-plans-scope-boundary-audit-abf92502/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)