# Ecology Observations Record Sequence Diff

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

Computes a record-level diff between two sequences of ecology observation records, separating true record insertions/deletions from reordering of surviving records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ecology-observations/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035164/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-record-sequence-diff-bb15e068
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E8Qd97fTxAEKSSoO0Ck6n

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-record-sequence-diff-bb15e068 -d '<json body>'
```

Example prompt: Compare these two ecology observation record sequences and tell me which records were actually inserted or deleted versus which ones just got reordered — the data class is public and all metadata is non-personal.

## When to prefer this

Choose this endpoint when you need to audit changes between two snapshots of an ecology observation, event, taxon, or method record list and specifically need to distinguish true record additions/removals from positional reordering of unchanged records. Prefer it over generic diff tools when the domain is ecology/environmental observation data with public or synthetic classification requirements and non-personal metadata constraints.

## Known failure modes

- Input arrays exceed 32-item limit — request rejected
- dataClass not set to 'public' or 'synthetic' — validation error
- nonpersonalMetadata is not explicitly set to true — request rejected
- Malformed array items — parsing or schema error
- Empty or identical before/after arrays — trivial or empty diff returned

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for public dataset/observation/event/taxon/method Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured breakdown of record-level changes between the before and after sequences, distinguishing genuine insertions and deletions from positional reordering of surviving records. Does not independently certify the data — analysis is based solely on the supplied records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "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-record-sequence-diff-bb15e068/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)