# Tool Context - Provenance Edge Audit

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

Binds tool-output edges to exact call, contract, and result pins to audit provenance of agent tool invocations, without persisting personal data.

## Facts

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

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-context-provenance-edge-audit-060c29df -d '<json body>'
```

Example prompt: Audit the provenance edges for these 5 tool calls and their outputs — bind them to their exact call and result pins, using public data class and nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need to audit or validate the provenance linkage between tool calls, their output edges, and contract/result pins in an agentic workflow — especially for compliance or traceability purposes where you need an offline, nonpersonal metadata audit trail. Not suitable if you need to confirm actual tool execution or delivery of results to users.

## Known failure modes

- Missing or empty 'calls', 'edges', or 'outputs' arrays cause validation errors
- Arrays exceeding 32 items are rejected
- dataClass not set to 'public' or 'synthetic' causes rejection
- nonpersonalMetadata not set to true (const) causes rejection
- Mismatched array lengths between calls, edges, and outputs may yield incomplete bindings
- Endpoint does not verify actual tool execution, only metadata edge bindings

## How this service works

Bind supplied tool-output edges to exact call, contract and result pins. A matching metadata edge does not prove the tool ran or that its result reached a user. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns provenance edge bindings that link each supplied tool output to its originating call and contract/result pins. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. Does not confirm that the tool actually ran or that its result reached a user.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "calls": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "outputs": {
   "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/tool-context-provenance-edge-audit-060c29df/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)