# Meeting Records Scope Boundary Audit

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

Filters a supplied batch of meeting records by exact meeting ID/revision, allowed agenda IDs, and a caller-declared half-open time window, returning only the records that fall within those scope constraints.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/meeting-records/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038295/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meeting-records-scope-boundary-audit-03878cdd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xrCJUJdY7BFk3BOdOINlu

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 meeting-records-scope-boundary-audit-03878cdd -d '<json body>'
```

Example prompt: Filter these 12 meeting records to only those matching meetingId 'MTG-2024-007', revision 'v3', agendaIds ['AGD-01','AGD-02'], and a time window from 2024-03-01T09:00:00Z to 2024-03-01T17:00:00Z — use public data class and nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need deterministic, scope-bounded filtering of typed nonpersonal meeting metadata — specifically when you must restrict records to an exact meetingId/revision combination, a whitelist of agendaIds, and a precise half-open time window. It is appropriate for compliance auditing, pre-archival checks, or governance workflows where offline, typed metadata filtering is needed without any recording access, participant identity inference, or completeness guarantees.

## Known failure modes

- Empty result set if no records match all scope constraints simultaneously
- Validation error if records array has fewer than 1 or more than 32 items
- Schema rejection if dataClass is not exactly 'public' or 'synthetic'
- Error if nonpersonalMetadata is not set to true (const constraint)
- Rejection if startsAt or endsAt are malformed timestamp strings
- Timeout or error if revision or meetingId does not match any submitted records

## How this service works

Filter supplied meeting records by exact meeting/revision, allowed agenda IDs and caller-declared half-open time window. No recording access, participant identity or completeness inference. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns the subset of submitted meeting records (up to 32) that satisfy all declared scope constraints: matching meetingId, revision, permitted agendaIds, and falling within the half-open [startsAt, endsAt) time window. Results reflect typed nonpersonal metadata only, with no recording access or participant identity. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "endsAt": {
   "type": "string"
  },
  "records": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "revision": {
   "type": "string"
  },
  "startsAt": {
   "type": "string"
  },
  "agendaIds": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "meetingId": {
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

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