# local.settings.json Change Audit & Validation

> local.settings.json Change Audit & Validation 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-22).

Audits before/after JSON changes for local.settings.json files, reporting added/removed/changed paths, JSON pointer violations, and schema rule errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-local-settings-json-cd438f3c-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/local-settings-json-change-audit-validation-e6ea4bc6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2ovTPmFd8T9fPHJSJe1K6

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 local-settings-json-change-audit-validation-e6ea4bc6 -d '<json body>'
```

Example prompt: Can you audit my local.settings.json changes? Here's the before version: {} and the after version where I added a new connection string — check what paths changed and whether any schema rule violations were introduced or resolved.

## When to prefer this

Use this endpoint when you need to audit before-and-after changes to a local.settings.json file specifically, with validation against a pinned SchemaStore definition. It is ideal for CI/CD pre-commit checks, pull request reviews of Azure Functions configuration, or any workflow where you need to understand exactly which JSON paths changed and whether those changes introduced or resolved schema errors. Not suitable for deployment validation, security auditing, or non-JSON config formats.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted for before or after fields — parse error
- Schema validation unavailable if SchemaStore definition is outdated on host
- Non-JSON formats (YAML, TOML) are not parsed and will fail

## How this service works

Change audit: local.settings.json: Audit JSON changes and validate before/after for local.settings.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 audit report listing all added, removed, and changed JSON paths between the before and after documents, along with any JSON pointer violations, schema rule violations, and a breakdown of errors that were introduced or resolved by the change — validated against a pinned SchemaStore definition for local.settings.json.

## 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/local-settings-json-change-audit-validation-e6ea4bc6/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)