# Spectrometry Records - Schema Directionality Analysis

> Spectrometry Records - Schema Directionality Analysis is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035175/call, status unknown (last checked 2026-10-20).

Compares closed export-field schema directionality between 'before' and 'after' spectrometry record sets to detect structural divergence in field ordering or schema orientation.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/spectrometry-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035175/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spectrometry-records-schema-directionality-analysis-85706b9f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NyK39nTmzdTGyAFCC-jHd

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 spectrometry-records-schema-directionality-analysis-85706b9f -d '<json body>'
```

Example prompt: Compare the schema directionality of these two batches of spectrometry records — use 'public' data class and set nonpersonal metadata to true; I want to know if any closed export fields have shifted direction between the before set and the after set.

## When to prefer this

Use this endpoint when you need to programmatically compare the schema directionality (field orientation/ordering) of closed export fields across two versions of spectrometry records, particularly when validating pipeline changes, synthetic data generation, or pre-release export audits. Prefer this over generic schema diff tools when working specifically with spectrometry record formats and needing a per-field directionality signal rather than a raw diff.

## Known failure modes

- 'before' array is empty or missing (minItems:1 required) — validation error returned
- 'after' array exceeds 32 items — request rejected with schema validation error
- nonpersonalMetadata not set to true (const:true) — request fails schema validation
- dataClass value outside 'public' or 'synthetic' enum — rejected
- Malformed record objects in before/after arrays causing parsing failure
- Network or payment authorization failure via x402 protocol

## 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 analysis of schema directionality differences between the 'before' and 'after' spectrometry record arrays, indicating whether closed export fields have shifted orientation or ordering, based on the supplied records — this is not independent certification but a comparison of caller-supplied 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/spectrometry-records-schema-directionality-analysis-85706b9f/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)