# Protein Measurements Record Sequence Diff

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

Computes the difference between two ordered sequences of protein/isoform/sequence-pinned measurement records, isolating true record insertions and deletions from reordering effects.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/protein-measurements/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035158/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/protein-measurements-record-sequence-diff-7e386c73
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2oB_DaGMUY9G8P3RLW1g9

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

Example prompt: I have two snapshots of a protein measurement dataset — the before array has up to 32 records and so does the after — can you run a record sequence diff on them using the 'public' data class to show me exactly which records were inserted or deleted, separate from any reordering?

## When to prefer this

Use this endpoint when you need to precisely distinguish genuine record insertions and deletions from positional reordering within protein, isoform, or sequence-pinned measurement datasets. It is purpose-built for supplied-record analysis (not independent certification), making it appropriate for audit, versioning, and pipeline validation workflows where up to 32 records are compared per call.

## Known failure modes

- Array exceeds 32 items — returns validation error
- Missing required nonpersonalMetadata:true field — request rejected
- Invalid dataClass value outside enum — schema validation failure
- Empty before and after arrays — returns empty diff with no changes
- Malformed array entries inconsistent with protein measurement schema — may return partial or error response

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for protein/isoform/sequence-pinned measurement Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured diff indicating which records were inserted and which were deleted between the before and after arrays, explicitly separated from any reordering of surviving records — enabling precise audit of protein/isoform/sequence-pinned measurement changes.

## 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/protein-measurements-record-sequence-diff-7e386c73/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)