# Payment Quotes - Provenance Edge Audit

> Payment Quotes - Provenance Edge Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.0453/call, status unknown (last checked 2026-10-16).

Binds prepared-purchase metadata to exact quote resources and input digest declarations within a network frame, validating provenance linkage offline without authorization or settlement.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/payment-quotes/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.0453/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-quotes-provenance-edge-audit-6a63c22a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QU7HT-gCpyzdatm9zww-p

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-provenance-edge-audit-6a63c22a -d '<json body>'
```

Example prompt: Can you run a provenance edge audit on these 3 prepared purchase entries and 3 payment quotes using public data class — I need to confirm that the quote resources and input digests are correctly bound to the right edges in the network frame?

## When to prefer this

Choose this endpoint when you need offline, non-authoritative validation that prepared-purchase metadata is correctly bound to specific quote resources and edge declarations within a network frame — specifically when you do not need authorization signatures, facilitator calls, or proof of settlement. It is ideal for pre-settlement integrity checks on public or synthetic nonpersonal metadata batches of up to 32 items.

## Known failure modes

- Mismatched array lengths between edges, quotes, and prepared items cause validation failure
- Exceeding 32 items per array returns a schema validation error
- Supplying personal or non-synthetic/non-public data class values is rejected by the const constraint
- Missing nonpersonalMetadata:true field causes request rejection
- Invalid or malformed edge/quote identifiers result in unresolvable binding errors
- Network frame context mismatch leads to cross-frame binding failure

## How this service works

Bind prepared-purchase metadata to exact quote resource and input digest declarations within a network frame. No authorization signatures, facilitator calls or proof of settlement. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns an audit result indicating whether the supplied prepared-purchase metadata is correctly bound to the specified quote resources and edge declarations within the network frame, including input digest validation status. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "quotes": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "prepared": {
   "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-provenance-edge-audit-6a63c22a/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)