# Package Manifests - Revision Delta Map

> Package Manifests - Revision Delta Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.021309/call, status unknown (last checked 2026-11-04).

Computes the delta between two revisions of caller-supplied package release and file-inventory manifests, enumerating owner, subject, revision, content, and scope pin changes by stable record ID.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/package-manifests/revision-delta-map?utm_source=zero.xyz
- Price: $0.021309/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/package-manifests-revision-delta-map-07a6921b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mOerRBA6j24_dtoixEybe

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 package-manifests-revision-delta-map-07a6921b -d '<json body>'
```

Example prompt: Compare these two package manifests for me — here's the before list and the after list, both using public data class — and tell me which records changed by stable ID, including any owner, subject, revision, content, or scope pin differences.

## When to prefer this

Use this endpoint when you need a structured, record-level diff of two package manifest snapshots without any registry resolution, dependency graph computation, or code execution. It is ideal for auditing manifest lineage changes, detecting unauthorized modifications to owner or scope pin fields, and reconciling manifests across team handoffs. Prefer it over full dependency graph tools when you only need manifest-level revision tracking on caller-supplied data up to 32 KiB.

## Known failure modes

- Input exceeds 32 KiB limit — request rejected
- before or after arrays exceed 32 items each — validation error
- dataClass not one of 'public' or 'synthetic' — schema validation failure
- nonpersonalMetadata not set to true — const constraint violation
- Malformed or missing array entries — parsing error
- Result expired after 24-hour retention window — receipt metadata only available

## How this service works

Enumerate owner, subject, revision, content and scope pin changes by stable record ID in two supplied revisions for caller-supplied package release and file-inventory manifests. Manifest revision lineage only, not a resolved package dependency graph. No registry lookup, download, installation, code execution, vulnerability scan, publisher authentication or software-safety certification. Input limit: 32 KiB. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a delta map keyed by stable record ID, listing which records changed between the before and after manifest arrays, with per-record enumeration of owner, subject, revision, content, and scope pin changes. Does not resolve dependencies, perform registry lookups, or execute any downloads or scans. Results are retained for 24 hours; minimal receipt metadata for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/package-manifests-revision-delta-map-07a6921b/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)