# Grant Records Provenance Edge Audit

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

Binds a declared graph edge to both pinned endpoint nodes and the exact owner/subject, auditing provenance for grant record data supplied by the caller.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/grant-records/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045334/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/grant-records-provenance-edge-audit-1d6b8a49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PDEI1jn9NSlDEWezUMg50

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 grant-records-provenance-edge-audit-1d6b8a49 -d '<json body>'
```

Example prompt: Audit the provenance edges in my grant records dataset — I have up to 10 edges and 10 nodes, the data class is public and there's no personal metadata — can you verify that each edge is correctly bound to its pinned endpoints and the right owner/subject?

## When to prefer this

Choose this endpoint when you need to audit and validate the provenance linkage of graph edges in grant records specifically, ensuring edges are correctly bound to pinned nodes and owner/subject pairs. Prefer this over generic graph validation tools when working within the grant records domain and when caller-supplied record analysis (not independent certification) is sufficient.

## Known failure modes

- Invalid edge or node array (empty or exceeds 32 items) returns validation error
- dataClass value not in allowed enum ('public','synthetic') causes rejection
- nonpersonalMetadata not set to true (const) causes request failure
- Malformed edge or node objects may return binding failure with details
- Mismatched owner/subject declarations result in provenance mismatch report

## 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 an audit report indicating whether each declared edge is correctly bound to both its pinned endpoint nodes and the exact owner/subject pair, based on the caller-supplied records. Does not provide independent certification — analysis is based solely on supplied record data.

## 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/grant-records-provenance-edge-audit-1d6b8a49/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)