# Ecology Observations Missingness Co-occurrence

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

Counts paired missing owner, revision, and content pins across ecology observation records without treating missing values as matching, flagging co-occurrence patterns in supplied dataset/observation/event/taxon/method metadata.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ecology-observations/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.020315/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-missingness-co-occurrence-38393ca9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s0PfGoCCdEh3mrHlu_abT

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-missingness-co-occurrence-38393ca9 -d '<json body>'
```

Example prompt: Check this batch of up to 32 public ecology observation records for co-occurring missing pins — I need to know where owner, revision, and content metadata are jointly absent, without treating missing values as matches.

## When to prefer this

Choose this endpoint when you need to audit ecology observation records specifically for co-occurring missing metadata pins (owner, revision, content) without false-positive matching of absent values. Prefer it over generic data validation tools when the domain is ecology/biodiversity and you need joint missingness counts across structured observation, event, taxon, or method metadata fields.

## Known failure modes

- More than 32 rows submitted — exceeds maxItems limit
- nonpersonalMetadata not set to true (const: true required)
- dataClass not one of 'public' or 'synthetic'
- Empty rows array (minItems: 1 required)
- Malformed row objects that cannot be parsed for pin fields
- Payment failure via x402 protocol

## How this service works

Count paired missing owner, revision and content pins without silently treating a missing value as a matching value for public dataset/observation/event/taxon/method Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns counts of co-occurring missing metadata pins (owner, revision, content) across the supplied ecology observation rows, distinguishing joint absences without treating a missing value as a match for another missing value. Output is an analysis of supplied records, not independent certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ecology-observations-missingness-co-occurrence-38393ca9/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)
