# Publication Release Comparison

> Publication Release Comparison is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.017004/call, status unknown (last checked 2026-10-21).

Compare two versions of a public or synthetic publication artifact to enumerate changed fields, findings, and source IDs between releases

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/publications/compare?utm_source=zero.xyz
- Price: $0.017004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-release-comparison-70e78318
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hRIcwhlgfzlZAg3SPFw9X

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-release-comparison-70e78318 -d '<json body>'
```

Example prompt: I have two versions of a public publication artifact — the original release and the updated one. Can you compare them and tell me which fields, findings, and source IDs changed between the two?

## When to prefer this

Use this endpoint when you have two caller-supplied, integrity-valid publication artifacts (public or synthetic) and need a structured enumeration of what changed — fields, findings, and source IDs — without triggering any source fetching, database access, causal explanation, or editorial workflow. Prefer this over general diff tools when working specifically with publication-domain artifacts that require integrity validation and structured output scoped to findings and source references.

## Known failure modes

- Invalid or non-integrity-valid artifact supplied — endpoint rejects non-public/non-synthetic data classes
- Mismatched publication types between before and after artifacts — may yield unexpected diff output
- Malformed JSON in either artifact — request fails with validation error
- Supplying 'same-as-before' for the 'after' field when no prior state exists — undefined behavior
- Payment failure via x402 protocol — call not executed

## How this service works

Compare two caller-supplied, integrity-valid public/synthetic artifacts of the same publication; enumerate changed fields, findings and source IDs without returning draft text. No database, source fetching, causal explanation or editorial approval.

## Output

A structured enumeration of changed fields, changed findings, and changed source IDs between the two supplied publication artifacts. No draft text is returned, and no database lookups or source fetching are performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "anyOf": [
    {
     "type": "object"
    },
    {
     "type": "string",
     "const": "same-as-before"
    }
   ]
  },
  "before": {
   "type": "object"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/publication-release-comparison-70e78318/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)