# Publication Records Scope Boundary Audit

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

Validates that bibliographic publication records conform to declared owner, subject, revision, and allowed scope labels, flagging any scope violations without granting independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038332/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-scope-boundary-audit-85bcebdb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nxh2e5wcvCHq38jqHyHut

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 publication-records-scope-boundary-audit-85bcebdb -d '<json body>'
```

Example prompt: Audit these 5 publication records for scope boundary compliance — the owner reference is 'oxford-press-001', subject reference is 'climate-science', revision is 'v2.3', allowed scopes are ['research','public-domain'], and data class is 'public' with nonpersonal metadata confirmed.

## When to prefer this

Choose this endpoint when you need to enforce strict scope boundary compliance on a batch of bibliographic or publication records against declared owner, subject, revision, and label constraints — particularly for governed document repositories, academic publishing pipelines, or bibliographic metadata audits where records must stay within pinned scope labels. Not suitable for independent certification or permission granting.

## Known failure modes

- Missing required ownerRef or subjectRef causes validation rejection
- Rows array empty or exceeds 32-item limit returns a bounds error
- Invalid dataClass value outside enum triggers schema error
- allowedScopes array empty or exceeds 16 items causes rejection
- nonpersonalMetadata not set to true (const) results in request failure
- Malformed revision string may produce unmatched audit results

## 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/DOI/edition-pinned bibliographic Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured audit report identifying which supplied publication records violate the declared owner, subject, revision, or allowed scope constraints, along with details of which label or pin failed. Does not grant permissions or certify records independently.

## 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/publication-records-scope-boundary-audit-85bcebdb/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)