# Polymer Measurements - Schema Directionality

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

Compares closed export-field directionality in supplied polymer measurement records without independent certification.

## Facts

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

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 polymer-measurements-schema-directionality-09a7a690 -d '<json body>'
```

Example prompt: Compare the schema directionality of these two polymer measurement record sets — I have a before array with my original records and an after array with the updated ones, the data class is synthetic, and nonpersonal metadata is true.

## When to prefer this

Use this endpoint when you need to compare schema directionality specifically for polymer measurement records between two snapshots (before/after), and your data is classified as either public or synthetic non-personal data. Prefer this over generic schema diff tools when the domain is polymer measurements and you need export-field directional consistency analysis rather than raw content comparison.

## Known failure modes

- before array is empty or exceeds 32 items — validation error
- after array exceeds 32 items — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not exactly true (const constraint) — rejected
- malformed or non-array input for before/after fields — schema error
- payment not included or insufficient — 402 payment 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 structured analysis of export-field schema directionality differences between the supplied before and after polymer measurement record arrays, identifying whether field directions are consistent, changed, or misaligned — scoped to closed export fields only, not an 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/polymer-measurements-schema-directionality-09a7a690/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)