# Change Audit for .putout.json

> Change Audit for .putout.json 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 changes for .putout.json files, reporting added/removed/changed paths, rule violations, and introduced/resolved errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-putout-json-f7209940-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/change-audit-for-putout-json-227e03e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ir7m9DyzGw9IbNdutZFmA

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-for-putout-json-227e03e6 -d '<json body>'
```

Example prompt: Can you audit the change I made to my .putout.json — here's the before and after — and tell me if any rule violations were introduced, what paths changed, and whether any new errors were added?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a .putout.json configuration file against a pinned SchemaStore definition, with structured reporting of diffs and rule violations. It is purpose-built for the putout linting tool's config format and reports both structural changes and schema compliance, making it better than a generic JSON diff tool for this specific config type.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation not performed
- Invalid JSON submitted (not parseable) — error returned
- Schema definition unavailable or stale on provider's end — results may be incomplete

## How this service works

Change audit: .putout.json: Audit JSON changes and validate before/after for .putout.json. 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 paths that were added, removed, or changed between the before and after documents, rule violations detected against the SchemaStore definition for .putout.json, and a list of errors that were introduced or resolved by the change. Up to 100 KB per document is supported.

## 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-for-putout-json-227e03e6/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)