# Bibliographies - Scope Boundary Audit

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

Validates that bibliography records conform exactly to declared owner, subject, revision, and allowed scope labels, without granting permissions or certifying ownership.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/bibliographies/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038339/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bibliographies-scope-boundary-audit-27310fba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CXND9lstmY_DpWTa_5ugm

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 bibliographies-scope-boundary-audit-27310fba -d '<json body>'
```

Example prompt: Can you audit these 5 bibliography rows against ownerRef 'lib-org-42', subjectRef 'history-dept', revision 'v3.1', and allowed scopes ['public','archive'], with dataClass set to 'public' and nonpersonalMetadata true, to make sure none of them cross scope boundaries?

## When to prefer this

Use this endpoint when you need to enforce exact scope boundary compliance on bibliography records before publication, release, or governance review — particularly when records must be pinned to a specific owner, subject, revision, and a whitelist of allowed scopes. Prefer this over generic metadata validators when the bibliography domain's scope-label governance model is required. Not suitable for ownership certification or permission granting.

## Known failure modes

- Rows array exceeds 32 items — request rejected
- allowedScopes array exceeds 16 items — request rejected
- Missing required nonpersonalMetadata:true field — validation error
- Invalid dataClass value outside 'public' or 'synthetic' enum — rejected
- Malformed ownerRef or subjectRef strings — schema validation failure
- Empty rows array (minItems:1 not met) — rejected
- Network or payment (x402) authentication failure — no result returned

## How this service works

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

## Output

Returns a structured audit report indicating whether each supplied bibliography row satisfies the exact declared owner reference, subject reference, revision pin, data class, and allowed scope labels. Reports scope boundary violations or confirmations per record; does not grant permissions or independently certify ownership — it is a 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/bibliographies-scope-boundary-audit-27310fba/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)