# Procurement Notices - Schema Directionality Analysis

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

Compares export-field directionality in closed procurement notice records by analyzing 'before' and 'after' field sets against a supplied schema contract.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/procurement-notices/schema-directionality?utm_source=zero.xyz
- Price: $0.035283/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/procurement-notices-schema-directionality-analysis-07d21885
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q4sF78k_7lQm0abXyTms1

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 procurement-notices-schema-directionality-analysis-07d21885 -d '<json body>'
```

Example prompt: Compare the schema directionality for a public procurement notice — here are the before fields [fieldA, fieldB] and the after fields [fieldA, fieldC], using public data class and no extra fields allowed.

## When to prefer this

Use this endpoint when you need to programmatically validate that procurement notice schema fields have shifted in the expected direction between two versions — particularly when auditing closed export records for field-level contract compliance. Prefer this over general schema diffing tools when the context is specifically procurement notices with public or synthetic data classification requirements.

## Known failure modes

- Empty 'before' array when minItems:1 is required returns validation error
- Arrays exceeding 32 items each trigger schema rejection
- Invalid dataClass value outside 'public' or 'synthetic' enum causes rejection
- Missing nonpersonalMetadata:true constant causes request failure
- Malformed field entries in before/after arrays result in parsing errors

## 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 directionality analysis comparing the supplied 'before' and 'after' field arrays against the schema contract, highlighting fields that were added, removed, or changed direction, along with any mismatches or compliance flags relative to the declared dataClass and consumer field tolerance.

## 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/procurement-notices-schema-directionality-analysis-07d21885/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)