# Foundry VTT Base Package Manifest JSON Change Audit

> Foundry VTT Base Package Manifest JSON Change Audit is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-24).

Validates and audits JSON changes between before/after versions of a Foundry VTT base package manifest, reporting added/removed/changed paths and schema rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-foundry-vtt-base-package-m-deec15fc-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-vtt-base-package-manifest-json-change-audit-c3703cd4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VTGGbVummFKmb60hggovE

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 foundry-vtt-base-package-manifest-json-change-audit-c3703cd4 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Foundry VTT base package manifest? Here's the before version and the after version — I want to know what JSON paths changed and whether I introduced any schema violations.

## When to prefer this

Choose this endpoint when you need schema-aware diff analysis of Foundry VTT base package manifests specifically, using a pinned SchemaStore definition. It is more precise than a generic JSON diff tool because it cross-references the Foundry VTT schema to distinguish valid changes from rule violations. Prefer it over generic JSON validators when you need both structural diffing and schema compliance in a single call.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input submitted instead of JSON — not supported
- Network or payment authorization failure — no audit returned

## How this service works

Change audit: Foundry VTT - Base package Manifest: Audit JSON changes and validate before/after for Foundry VTT - Base package Manifest. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations, added/removed/changed paths and introduced/resolved errors. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one two-document change audit.

## Output

Returns a structured report of JSON pointer differences (added, removed, and changed paths) between the before and after documents, plus any schema rule violations introduced or resolved relative to the pinned Foundry VTT base package manifest SchemaStore definition.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "default": {
    "agent_market_example": true
   },
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  },
  "before": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-vtt-base-package-manifest-json-change-audit-c3703cd4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)