# Study Notes Scope Boundary Audit

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

Filters study note metadata by exact notebook ID and allowed claim-kind declarations, validating scope boundaries without inferring truth or learner profiles.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/study-notes/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038296/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/study-notes-scope-boundary-audit-d16cdc66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zQsklQAV3F9yJjJ8md2VU

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 study-notes-scope-boundary-audit-d16cdc66 -d '<json body>'
```

Example prompt: Filter my study notes in notebook 'nb-20240501' against allowed claim kinds ['fact','definition','summary'] using the public data class — just check scope boundaries on the nonpersonal metadata, no profile inference.

## When to prefer this

Choose this endpoint when you need to filter or audit study note metadata strictly by notebook scope and declared claim-kind allowlists, without any AI inference, learner profiling, or claim completeness checking. It is ideal for offline, privacy-preserving metadata validation workflows where only typed nonpersonal metadata is acceptable and results are needed quickly with short retention.

## Known failure modes

- Missing or invalid notebookId causes rejection of the entire batch
- Notes array exceeding 32 items returns a validation error
- allowedKinds array with more than 3 entries is rejected
- dataClass value outside ['public','synthetic'] enum causes error
- nonpersonalMetadata not set to true (const) causes schema validation failure
- Empty notes array (fewer than 1 item) returns an error

## How this service works

Filter note metadata by exact notebook and allowed claim-kind declarations before selection. No inferred truth, learner profile or claim completeness. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns filtered note metadata that passes the scope boundary check — only notes within the specified notebookId and matching one of the allowedKinds claim types are included. Result includes a minimal receipt metadata record retained for 90 days; full result retained for 24 hours. No learner profile data, inferred truth, or claim completeness information is returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "notes": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "notebookId": {
   "type": "string"
  },
  "allowedKinds": {
   "type": "array",
   "maxItems": 3,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/study-notes-scope-boundary-audit-d16cdc66/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)