# Grant Records - Scope Boundary Audit

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

Validates that grant records conform to exact declared owner, subject, revision, and allowed scope labels, flagging any scope boundary violations without granting access or permissions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/grant-records/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038334/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/grant-records-scope-boundary-audit-7ffe8ed0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G8lXoTbMJsn3PkeJWUhyx

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 grant-records-scope-boundary-audit-7ffe8ed0 -d '<json body>'
```

Example prompt: Can you audit these 10 grant records for scope boundary compliance — the owner is 'agency-grants-div', subject is 'opportunity-2024-Q2', revision is 'rev-003', and the allowed scopes are ['federal','state'] with public data class and nonpersonal metadata?

## When to prefer this

Choose this endpoint when you need to audit grant records for exact scope boundary compliance against declared owner, subject, revision, and allowed scope labels — particularly for agency, opportunity, program, or jurisdiction-pinned grants. It is best suited for batch analysis of up to 32 records at a time with public or synthetic nonpersonal data. Prefer this over general data validation tools when working specifically in grants management contexts where scope label enforcement is the primary concern.

## Known failure modes

- Rows array empty or exceeds 32-item limit — request rejected
- allowedScopes array empty or exceeds 16-item limit — validation error
- nonpersonalMetadata not set to true — required constant constraint violation
- Invalid dataClass value outside 'public' or 'synthetic' enum — rejected
- Missing ownerRef, subjectRef, or revision fields — incomplete audit context error
- Payment of 0.038334 USDC not completed via x402 — 402 Payment Required response

## How this service works

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

## Output

The endpoint returns a record-level analysis report identifying which grant rows violate the declared scope boundaries, including mismatches between owner/subject/revision pins and the supplied allowed scope labels. Results are analytical findings only and do not confer access, permissions, or 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/grant-records-scope-boundary-audit-7ffe8ed0/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)