# Container Structure Test JSON Change Audit

> Container Structure Test 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).

Audits before/after JSON document pairs against the Container Structure Test schema, reporting added, removed, and changed paths plus introduced or resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-container-structure-test-3d7154f6-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/container-structure-test-json-change-audit-2a7e4a52
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ehs3P1A4IXyzIHWAjfGtK

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 container-structure-test-json-change-audit-2a7e4a52 -d '<json body>'
```

Example prompt: Can you audit the change I made to my container-structure-test.json — here's the before and after — and tell me which paths were added or removed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you need to validate a specific before/after change to a Container Structure Test JSON configuration against the SchemaStore schema definition, particularly to detect newly introduced or resolved validation errors. It is ideal for CI/CD workflows, code review automation, or configuration auditing where you want structured JSON pointer–level diffing combined with schema validation in a single call. Not suitable for YAML/TOML configs, non–Container Structure Test schemas, or documents exceeding 100 KB.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- Nesting depth exceeds 32 levels — parsing fails
- Input is not valid JSON (YAML/TOML not supported) — parsing error returned
- Missing 'after' field — defaults to example object, may produce unexpected results
- Schema unavailable or pinned definition mismatch — validation may be incomplete

## How this service works

Change audit: Container Structure Test: Audit JSON changes and validate before/after for Container Structure Test. 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 report listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations that were introduced or resolved relative to the Container Structure Test SchemaStore definition. Limited to documents up to 100 KB each and 32 nesting levels.

## 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/container-structure-test-json-change-audit-2a7e4a52/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)