# Change Audit: launchsettings.json

> Change Audit: launchsettings.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-22).

Compares two versions of a launchsettings.json document, reporting added/removed/changed JSON paths and schema validation errors introduced or resolved between them.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-launchsettings-json-da9ea985-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/change-audit-launchsettings-json-1108fdc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MQF6HcsnC9g-0QkMFExM1

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-launchsettings-json-1108fdc0 -d '<json body>'
```

Example prompt: I just updated my launchsettings.json — can you audit the change and tell me what paths were added, removed, or modified, and whether my edits introduced or fixed any schema violations? Here's the before version: {} and the after version: {"profiles":{"MyApp":{"commandName":"Project","applicationUrl":"https://localhost:5001"}}}

## When to prefer this

Choose this endpoint when you specifically need to audit two-document before/after diffs of launchsettings.json files with pinned SchemaStore validation, particularly in developer workflows, CI pipelines, or code review automation where you want both a structural diff and schema error delta in a single call. Prefer alternatives if you need YAML/TOML support, security analysis, deployment validation, or schema coverage for other JSON config file types.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing may fail or be truncated
- Malformed JSON input — validation cannot proceed
- Network or payment gateway error — no result returned
- Schema definition unavailable or outdated — validation may be incomplete

## How this service works

Change audit: launchsettings.json: Audit JSON changes and validate before/after for launchsettings.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 listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition for launchsettings.json. No YAML/TOML parsing or deployment/security guarantees are included.

## 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-launchsettings-json-1108fdc0/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)