# Evidence-Frame Compatibility Check

> Evidence-Frame Compatibility Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010501/call, status unknown (last checked 2026-10-19).

Validates up to ten claim-evidence pairs against a versioned rule set, flagging unsupported frame transfers and missing information without performing prose interpretation or truth certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/evidence/frame-compatibility?utm_source=zero.xyz
- Price: $0.010501/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evidence-frame-compatibility-check-f2e5f92c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ju-h3_G9IiY6EMUIP3naG

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 evidence-frame-compatibility-check-f2e5f92c -d '<json body>'
```

Example prompt: Can you run a frame compatibility check on these five claim-evidence pairs I have — they're all public data — and tell me which ones have unsupported frame transfers or are missing information?

## When to prefer this

Choose this endpoint when you need to systematically check declared claim-evidence relationships against a finite versioned rule set and want explicit flags for unsupported frame transfers or missing information. It is not suitable when you need prose interpretation, truth certification, or inspection of source documents — use it specifically for structural frame compatibility validation of up to ten pairs per call.

## Known failure modes

- Exceeding 10 pairs returns a validation error
- Pairs with unknown frame combinations remain unresolved rather than flagged as errors
- Invalid dataClass enum value causes request rejection
- Empty pairs array fails minimum item constraint
- No external source inspection performed so errors in underlying sources are not detected

## How this service works

Check up to ten declared claim-evidence relationships against a finite, versioned rule set. Reports unsupported frame transfers and missing information. Unknown combinations remain unresolved. No prose interpretation, source inspection or truth certification. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns per-pair compatibility results indicating whether each claim-evidence relationship is supported, flagged for unsupported frame transfer, missing information, or left unresolved. Results are retained for 24 hours; minimal receipt metadata is stored for 90 days. No prose interpretation or source inspection is provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pairs": {
   "type": "array",
   "maxItems": 10,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evidence-frame-compatibility-check-f2e5f92c/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)