# Change Audit: ArchitectFX JSON Schema Validator

> Change Audit: ArchitectFX JSON Schema Validator 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-18).

Audits JSON document changes for ArchitectFX by comparing before/after snapshots, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-architectfx-74e6c41f-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-architectfx-json-schema-validator-27877149
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pNtUnrvGFySJ1L6yTvWhB

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-architectfx-json-schema-validator-27877149 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my ArchitectFX config — here's the before version and the after version — and tell me which JSON paths changed, what was added or removed, and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you specifically need to audit configuration changes for ArchitectFX JSON files and want schema-aware diff reporting (not just structural diffing). It uses a pinned SchemaStore definition for ArchitectFX, making it more precise than generic JSON diff tools. Prefer it when you need both a change report and schema violation tracking in a single call, especially in CI/CD or code-review workflows where ArchitectFX configs evolve over time.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting depth exceeds 32 levels — parsing fails
- Invalid JSON submitted (YAML or TOML not supported) — parse error returned
- Malformed request body — validation error
- Payment not processed — 402 response blocking access

## How this service works

Change audit: ArchitectFX: Audit JSON changes and validate before/after for ArchitectFX. 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 listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, based on a pinned ArchitectFX 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-architectfx-json-schema-validator-27877149/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)