# Package Manifests - Scope Boundary Audit

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

Validates that a package manifest's declared owner, subject, revision, and scope labels exactly match caller-supplied constraints, enforcing strict scope boundary rules without granting any permission or access.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/package-manifests/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038309/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/package-manifests-scope-boundary-audit-6522bc52
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Uyp01rUzPiCVHJ8nMk7lS

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 package-manifests-scope-boundary-audit-6522bc52 -d '<json body>'
```

Example prompt: Check whether this batch of package manifest rows has valid scope boundaries — the owner is 'acme-corp', subject is 'payments-service', revision is 'v2.4.1', and the allowed scopes are ['internal','restricted']; data class is 'public' and all metadata is nonpersonal.

## When to prefer this

Choose this endpoint when you need strict, deterministic scope boundary enforcement on caller-supplied package manifest rows against declared owner, subject, revision, and allowed scope label constraints — particularly in CI/CD pipelines, compliance workflows, or supply chain audits where exact conformance (not approximate matching) is required. Prefer this over general-purpose validation tools when the specific package manifest scope boundary semantics (owner/subject/revision/scope pinning) are the target of the audit.

## Known failure modes

- Missing required fields (ownerRef, subjectRef, revision, allowedScopes) returns a validation error
- rows array outside 1–32 item bounds causes rejection
- allowedScopes array outside 1–16 item bounds causes rejection
- dataClass value not in enum ['public','synthetic'] returns error
- nonpersonalMetadata not set to true (const) causes rejection
- Malformed or empty rows result in audit failure
- Network or payment failure returns 402 or 5xx error

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for caller-supplied package release and file-inventory Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured audit result indicating whether each supplied manifest row conforms to the exact declared owner, subject, revision, and allowed scope labels. Reports which rows pass or fail scope boundary enforcement, without granting any access or permission based on label matches. Analysis is of caller-supplied records only, not an independent certification.

## 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/package-manifests-scope-boundary-audit-6522bc52/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)