# Payment Quotes — Missingness Co-occurrence

> Payment Quotes — Missingness Co-occurrence is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.0203/call, status unknown (last checked 2026-10-23).

Counts the joint absence (co-occurrence of nulls) of quote amount, network, and payee references across a batch of payment quotes.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/payment-quotes/missingness-cooccurrence?utm_source=zero.xyz
- Price: $0.0203/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-missingness-co-occurrence-d345769f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VEBBJMUhhH63kPkzrQjfr

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-missingness-co-occurrence-d345769f -d '<json body>'
```

Example prompt: Can you check this batch of payment quotes and count how many are jointly missing their amount, network, and payee fields at the same time? The data is synthetic and all metadata is non-personal.

## When to prefer this

Use this endpoint when you need to quantify how often multiple payment quote fields are simultaneously absent — not just individually missing. Ideal for data quality pipelines that want to detect structural gaps in quote metadata (amount, network, payee) across a batch, especially when working with synthetic or public non-personal data. Prefer this over single-field coverage checks when joint absence patterns matter for downstream processing decisions.

## Known failure modes

- Array of quotes is empty or exceeds 32 items — validation error
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true — rejected by const constraint
- Malformed quote objects in the array — schema validation error
- Network timeout or service unavailability — HTTP 5xx response

## How this service works

Count joint absence of quote amount, network and payee references. Canonical zero-unit amounts remain supplied metadata; absence is not a diagnosis of endpoint failure. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns counts and patterns of jointly absent fields (quote amount, network, payee references) across the supplied payment quotes batch. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. Zero-unit amounts are treated as supplied metadata, not as missing values.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "quotes": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payment-quotes-missingness-co-occurrence-d345769f/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)