# Alloy Measurements - Schema Directionality

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

Compares closed export-field directionality in alloy measurement records, checking before/after field sets against supplied schema contracts.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/schema-directionality?utm_source=zero.xyz
- Price: $0.035193/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-schema-directionality-ddb534a1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_229LQRlVlZu2ibzt-p63b

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 alloy-measurements-schema-directionality-ddb534a1 -d '<json body>'
```

Example prompt: Can you compare the directionality of our alloy measurement export schema — here are up to 32 fields from the before snapshot and up to 32 from the after snapshot, data class is public, nonpersonal metadata is true, and the consumer allows extra fields?

## When to prefer this

Choose this endpoint when you need to compare the directional change of export fields in alloy measurement schemas between two snapshots (before/after), particularly when validating that a schema contract has not been improperly narrowed or expanded. Prefer this over generic schema diff tools when working specifically with alloy measurement records in public or synthetic data classes under a closed export-field contract.

## Known failure modes

- before array empty or exceeds 32 items — validation error
- after array exceeds 32 items — validation error
- nonpersonalMetadata not set to true (const:true) — rejected
- invalid dataClass value outside enum [public, synthetic] — schema error
- malformed field arrays — parse error
- payment failure — x402 authorization required

## How this service works

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

## Output

Returns a directionality analysis comparing the before and after field sets for alloy measurement export schemas, identifying whether fields were narrowed, expanded, added, or removed relative to the supplied record contract. This is a record-supplied analysis, not independent certification.

## 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/alloy-measurements-schema-directionality-ddb534a1/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)