# Procurement Notices - Provenance Edge Audit

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

Binds declared graph edges to pinned endpoint nodes and owner/subject supplier records, auditing provenance linkage in procurement notice data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/procurement-notices/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045335/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/procurement-notices-provenance-edge-audit-7cfa44e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__eo2zfcB7MTzJ59EW1iXi

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 procurement-notices-provenance-edge-audit-7cfa44e6 -d '<json body>'
```

Example prompt: Can you audit the provenance edges in this procurement notice graph — I have up to 10 edges and 10 nodes, all public data with non-personal metadata only — and check whether the declared edges are correctly bound to the pinned endpoints and the right owner/subject supplier records?

## When to prefer this

Use this endpoint when you need to audit the provenance linkage of declared graph edges in procurement notice data, specifically to confirm edges are bound to correct pinned endpoint nodes and owner/subject supplier records. Prefer this over general graph validation tools when working with procurement-domain supplier graphs and needing a structured provenance binding report tied to Maha Strategies' intel schema.

## Known failure modes

- Edge count exceeds maxItems (32) — request rejected
- Node count exceeds maxItems (32) — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true (const) — request rejected
- Edges reference nodes not present in the nodes array — audit may return unresolvable binding errors
- Malformed edge or node objects — schema validation failure

## How this service works

Bind a declared edge to both pinned endpoints and the exact owner/subject Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured audit report indicating whether each declared edge is correctly bound to both its pinned endpoint nodes and the corresponding owner/subject supplier records, flagging mismatches or unresolvable bindings. This is a supplied-record analysis result, not independent certification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nodes": {
   "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/procurement-notices-provenance-edge-audit-7cfa44e6/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)