# Ecology Observations - Schema Directionality

> Ecology Observations - Schema Directionality is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035163/call, status unknown (last checked 2026-10-16).

Compares closed export-field schema directionality across supplied ecology observation records to validate structural alignment without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ecology-observations/schema-directionality?utm_source=zero.xyz
- Price: $0.035163/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ecology-observations-schema-directionality-7f797dfb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VBQ3_I2bp3JM1aEbE3_sX

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-schema-directionality-7f797dfb -d '<json body>'
```

Example prompt: Compare the schema directionality of my ecology observation records — I have 5 items in the before set and 3 in the after set, using public data class, with nonpersonal metadata only enabled.

## When to prefer this

Use this endpoint when you need to validate the directionality and structural alignment of export fields in ecology observation records specifically, comparing a before and after snapshot of supplied records. It is suited for data pipelines where schema consistency must be confirmed prior to publishing or exporting ecology datasets, especially when nonpersonal metadata constraints apply.

## Known failure modes

- before array empty or exceeds 32 items — validation error
- after array exceeds 32 items — validation error
- nonpersonalMetadata not explicitly set to true — rejected by const constraint
- invalid dataClass value outside 'public' or 'synthetic' enum — rejected
- malformed request body — 400 error
- payment not provided — 402 error

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured comparison of schema directionality across the supplied ecology observation records, indicating whether the closed export-field structure is aligned and valid — without acting as independent certification. Highlights discrepancies between before and after record sets.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "consumerAllowsExtraFields": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ecology-observations-schema-directionality-7f797dfb/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)