# Change Audit for .vsconfig Files

> Change Audit for .vsconfig Files 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-19).

Validates and compares before/after JSON documents against the .vsconfig JSON schema, reporting added, removed, and changed paths along with introduced and resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-vsconfig-27f1956b-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-for-vsconfig-files-43bd05fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iywb9Q4nCZWTCcj6J5Qq0

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-vsconfig-files-43bd05fa -d '<json body>'
```

Example prompt: Can you audit my .vsconfig change — here's the before and after JSON — and tell me which paths were added, removed, or changed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you specifically need to audit changes to a .vsconfig file (Visual Studio component configuration) against its canonical JSON schema, and you want a structured diff that highlights both structural changes (added/removed/changed paths) and schema compliance transitions (newly introduced or resolved errors). Prefer this over generic JSON diff tools when schema-aware validation is needed for .vsconfig specifically.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing aborted
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Schema definition unavailable or stale on the server — audit may be incomplete

## How this service works

Change audit: .vsconfig: Audit JSON changes and validate before/after for .vsconfig. 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 diff of the two .vsconfig JSON documents, including JSON pointers for added, removed, and modified paths, a list of schema rule violations introduced by the change, and a list of violations resolved by the change — all evaluated against a pinned 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-for-vsconfig-files-43bd05fa/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)