# Ecology Observations Scope Boundary Audit

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

Validates ecology observation records against declared owner, subject, revision, and allowed scope labels to audit boundary compliance without granting access or certifying data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ecology-observations/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038315/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ecology-observations-scope-boundary-audit-2bd91b16
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__KUio_FgbJYjI-fdwbEW6

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 ecology-observations-scope-boundary-audit-2bd91b16 -d '<json body>'
```

Example prompt: Audit these 10 ecology observation rows against owner 'org-ecowatch-42', subject 'wetlands-survey-2024', revision 'v3', data class 'public', and allowed scopes ['regional','national'] — flag any rows that violate the scope boundary, treating all metadata as nonpersonal.

## When to prefer this

Choose this endpoint when you need to programmatically audit ecology observation records for scope label compliance against declared ownership and revision metadata, particularly for public or synthetic datasets where governance boundaries must be enforced before downstream use. Prefer this over general data validation tools when the domain is ecological observation data and scope boundary enforcement (not data quality or content analysis) is the primary concern.

## Known failure modes

- Missing required ownerRef or subjectRef fields returns a validation error
- rows array empty or exceeding 32 items rejected with constraint violation
- nonpersonalMetadata must be explicitly set to true or request is rejected
- dataClass must be exactly 'public' or 'synthetic' — other values cause enum rejection
- allowedScopes array exceeding 16 items triggers constraint error
- Malformed revision string may cause unmatched audit results

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for public dataset/observation/event/taxon/method Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an analysis of each supplied ecology observation row against the declared owner reference, subject reference, revision, data class, and allowed scope labels — identifying which rows have non-compliant or out-of-boundary scope labels, without granting any access to underlying datasets or independently certifying the data.

## 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/ecology-observations-scope-boundary-audit-2bd91b16/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)