# Market Catalogues Scope Boundary Audit

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

Validates that supplied product catalogue records conform to declared owner, subject, revision, and allowed scope labels, flagging any scope violations without granting access or permissions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/market-catalogues/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038337/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/market-catalogues-scope-boundary-audit-a91c798b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ygn-NFarWrKZYgeQ7odWX

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 market-catalogues-scope-boundary-audit-a91c798b -d '<json body>'
```

Example prompt: Audit these 10 public product catalogue rows for our owner ref 'merch-0042', subject ref 'cat-electronics', revision 'r3', and allowed scopes ['retail','wholesale'] — flag any rows that fall outside the declared scope boundaries.

## When to prefer this

Choose this endpoint when you need to enforce declared scope label compliance on product catalogue records before reconciliation, publishing, or downstream processing, especially when you need an auditable, inspectable record of scope boundary violations tied to a specific owner, subject, and revision — without triggering any access grants or permissions changes.

## Known failure modes

- Invalid or missing ownerRef causes request rejection
- rows array empty or exceeds 32-item limit returns validation error
- allowedScopes array empty or exceeds 16-item limit returns error
- nonpersonalMetadata not set to true (const) causes schema rejection
- dataClass not one of 'public' or 'synthetic' causes enum validation failure
- Malformed row objects in the rows array may result in partial analysis or error

## How this service works

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

## Output

Returns an analysis of each supplied catalogue row indicating whether it conforms to the declared owner, subject, revision, and allowed scope labels, identifying rows that violate scope boundaries without granting any data access or permissions.

## 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/market-catalogues-scope-boundary-audit-a91c798b/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)