# omnisharp.json Change Audit & Validator

> omnisharp.json Change Audit & Validator 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-18).

Audits JSON changes between a before and after document for omnisharp.json, reporting added/removed/changed paths and introduced/resolved schema validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-omnisharp-json-297748be-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omnisharp-json-change-audit-validator-80f2bdcc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R0dnragj4FhjK7WkPV8TX

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 omnisharp-json-change-audit-validator-80f2bdcc -d '<json body>'
```

Example prompt: Can you audit my omnisharp.json change — here's the before config and the after config — 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

Choose this endpoint when you specifically need to audit changes to an omnisharp.json configuration file against its SchemaStore definition, comparing a before and after state to detect schema violations, added/removed/changed paths, and whether errors were introduced or resolved. It is purpose-built for omnisharp.json and uses a pinned schema definition, making it more reliable than a generic JSON schema validator for this specific file type.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (not parseable) — error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment failure — no audit result returned

## How this service works

Change audit: omnisharp.json: Audit JSON changes and validate before/after for omnisharp.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 change audit report including JSON pointers for all added, removed, and changed paths between the before and after documents, plus a list of schema rule violations introduced or resolved by the change, based on a pinned SchemaStore definition for omnisharp.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/omnisharp-json-change-audit-validator-80f2bdcc/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)