# Protein Measurements Schema Directionality

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

Compares before/after protein measurement field arrays to analyze schema directionality and detect export-field changes in closed record sets.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/protein-measurements/schema-directionality?utm_source=zero.xyz
- Price: $0.035157/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/protein-measurements-schema-directionality-d4da2c49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5tRPlCo-DLNg5qaRWfcYW

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

Example prompt: Compare my protein measurement schema fields — before I had fields [proteinId, concentration, timestamp] and after the update I have [proteinId, mass, purity, timestamp] — using public data class and flag that nonpersonal metadata is true, so I can see what changed directionally.

## When to prefer this

Choose this endpoint when you need to programmatically compare two snapshots of protein measurement schema fields to detect directional changes (additions, removals) in a closed export-field context, particularly when working with public or synthetic data classes and needing a lightweight metadata-level diff rather than raw data parsing.

## Known failure modes

- before array empty or exceeds 32 items — validation error
- after array exceeds 32 items — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation error
- nonpersonalMetadata not set to true (const constraint) — rejected
- malformed array entries — schema parse error
- payment not settled — 402 response

## How this service works

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

## Output

A structured report indicating the directional relationship between the before and after field arrays, highlighting added, removed, or changed export fields in the protein measurement schema, scoped to the specified data class without exposing raw cell data.

## 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/protein-measurements-schema-directionality-d4da2c49/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)