# Publication Records - Reference Integrity Map

> Publication Records - Reference Integrity Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035263/call, status unknown (last checked 2026-10-16).

Checks parent existence and detects cycles in owner and subject relationships within supplied publication record rows, reporting referential integrity issues without certifying the data independently.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/reference-integrity-map?utm_source=zero.xyz
- Price: $0.035263/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-reference-integrity-map-c942fb18
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m5UOF8N88lRsIQXvgTze0

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 publication-records-reference-integrity-map-c942fb18 -d '<json body>'
```

Example prompt: Can you check these 10 publication records for broken parent references and ownership cycles? The data is synthetic and contains only non-personal metadata — I want to know if any rows have missing parents or circular links before I import them.

## When to prefer this

Choose this endpoint when you need a lightweight, scoped integrity check on a small batch (up to 32 rows) of publication records before ingesting or publishing them, specifically to catch broken parent references and ownership/subject cycles. It is not an independent certification service — use it as a pre-flight validation step when your pipeline processes publication metadata with known owner and subject relationship fields.

## Known failure modes

- Rows array empty or exceeds 32-item limit — validation error returned
- dataClass not one of 'public' or 'synthetic' — rejected with schema error
- nonpersonalMetadata not explicitly set to true — request rejected
- Malformed row objects with missing required fields — partial or full analysis failure
- Cycles that span records outside the supplied batch may not be detected — limited to supplied data scope

## How this service works

Check parent existence and cycles within owner and subject Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-row analysis indicating whether each supplied publication record's parent exists and whether any cycles are present in owner or subject relationship chains, along with summary integrity findings. Does not certify records independently; analysis is scoped to the supplied rows.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "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/publication-records-reference-integrity-map-c942fb18/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)