# Tool Schemas - Provenance Edge Audit

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

Binds caller-supplied implementation-manifest edges to tool-schema declarations, linking owner, revision, input/output pins, and pinned implementation artifacts for provenance tracking.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045304/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-provenance-edge-audit-e964f1d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hvI20Folf1fLbs2SsKzcs

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 tool-schemas-provenance-edge-audit-e964f1d4 -d '<json body>'
```

Example prompt: Can you audit the provenance edges for these 3 tool schema contracts and bind them to their implementation artifacts and revision pins? All data is public and non-personal.

## When to prefer this

Choose this endpoint when you need to formally bind and audit provenance edges between tool schema declarations and their implementation manifests, particularly when tracking owner, revision, and pin-level linkage for governance or compliance purposes. It is specifically suited for offline, typed, non-personal metadata auditing of tool schemas in public or synthetic data classes. It does not validate deployed code conformity, so pair it with runtime checks if live conformance is needed.

## Known failure modes

- Invalid or mismatched edge/contract/implementation arrays (schema validation error)
- dataClass not set to 'public' or 'synthetic' (enum rejection)
- nonpersonalMetadata not set to true (const constraint violation)
- Array length outside 1-32 item bounds (min/max items violation)
- Declared artifact not found or unresolvable (provenance binding failure)
- Payment not processed — x402 payment required error

## How this service works

Bind caller-supplied implementation-manifest edges to tool-schema declaration owner, revision, input/output pins and a pinned implementation artifact. Matching declarations do not prove deployed code conformity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a provenance receipt confirming the binding of caller-supplied edges to tool schema declaration owners, revisions, input/output pins, and pinned implementation artifacts. Note: matching declarations do not prove deployed code conformity. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tool-schemas-provenance-edge-audit-e964f1d4/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)