# Change Audit: Foundry VTT System Data Template

> Change Audit: Foundry VTT System Data Template 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-16).

Audits JSON changes between before/after documents for Foundry VTT System Data Template, reporting added/removed/changed paths and schema validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-foundry-vtt-system-data-te-6b4ad77b-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-foundry-vtt-system-data-template-c8d16669
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R1R_FGA5lb6VtqetA1Sm_

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 change-audit-foundry-vtt-system-data-template-c8d16669 -d '<json body>'
```

Example prompt: Can you audit my Foundry VTT System Data Template JSON changes? Here's the before version and the after version — I want to know which paths changed, what schema violations were introduced or resolved, and any rule violations.

## When to prefer this

Use this endpoint when you specifically need to validate and diff JSON documents conforming to the Foundry VTT System Data Template schema, leveraging the pinned SchemaStore definition for accurate rule checking. Prefer this over generic JSON diff tools when you need schema-aware validation with error lifecycle tracking (introduced vs. resolved) for Foundry VTT game system data.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing fails
- Input is not valid JSON (e.g. YAML or TOML) — not supported
- Malformed request body — returns error
- Payment not completed — endpoint not accessible

## How this service works

Change audit: Foundry VTT - System Data Template: Audit JSON changes and validate before/after for Foundry VTT - System Data Template. 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

A structured audit report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations that were introduced or resolved, based on the pinned Foundry VTT System Data Template 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/change-audit-foundry-vtt-system-data-template-c8d16669/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)