# Payment Quotes - Schema Directionality Checker

> Payment Quotes - Schema Directionality Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035073/call, status unknown (last checked 2026-10-23).

Compares closed quote-ingestion field contracts across before/after snapshots to detect removals, type changes, and newly required fields across accepted payment networks.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/payment-quotes/schema-directionality?utm_source=zero.xyz
- Price: $0.035073/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-quotes-schema-directionality-checker-ff6ecc19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-2UJVwnoSep52NJ6JQq9w

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 payment-quotes-schema-directionality-checker-ff6ecc19 -d '<json body>'
```

Example prompt: Can you check whether the payment quote schema changed in a breaking way between our old field set and the new one for the public data class — specifically looking at network labels for both before and after snapshots?

## When to prefer this

Choose this endpoint when you need to audit schema evolution specifically for payment quote ingestion fields across one to three named payment networks, and want a structured non-breaking-change assessment without executing any protocol negotiation or modifying state. It is best for offline, typed, nonpersonal metadata comparison of closed field contracts in a before/after versioning scenario.

## Known failure modes

- Missing required 'before' or 'afterNetworks' fields returns validation error
- More than 3 networks supplied triggers maxItems constraint rejection
- nonpersonalMetadata not set to true causes request rejection
- dataClass value outside 'public' or 'synthetic' enum fails validation
- Before/after arrays exceeding 32 items are rejected
- Supplying personally identifiable data violates service contract

## How this service works

Compare closed quote-ingestion fields and accepted network labels for request narrowing. Adding an accepted label is not a break; no arbitrary schema or protocol negotiation is executed. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured report indicating schema directionality between before and after quote-ingestion snapshots, flagging field removals, type changes, and newly required fields per accepted network label. Results are retained for 24 hours; minimal receipt metadata for 90 days.

## 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"
  },
  "afterNetworks": {
   "type": "array",
   "maxItems": 3,
   "minItems": 1
  },
  "beforeNetworks": {
   "type": "array",
   "maxItems": 3,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payment-quotes-schema-directionality-checker-ff6ecc19/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)