# DocFx Config (docfx.json) Change Audit

> DocFx Config (docfx.json) Change Audit 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).

Validates and audits JSON changes between before/after versions of a DocFx Config (docfx.json) file, reporting added/removed/changed paths, JSON pointer violations, and introduced or resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-docfx-config-docfx-json-30dd08ac-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/docfx-config-docfx-json-change-audit-08314107
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AHv9qxhzup10DGqlCGDRw

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 docfx-config-docfx-json-change-audit-08314107 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my docfx.json — here's the before version and the after version — and tell me which JSON paths were added, removed, or changed, and whether any new schema errors were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you specifically need schema-aware change auditing for DocFx Config (docfx.json) files, including detection of introduced or resolved schema violations using a pinned SchemaStore definition. Prefer this over generic JSON diff tools when DocFx-specific rule validation matters, or when you need structured JSON pointer reporting rather than a plain text diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — validation may fail
- Invalid JSON submitted (non-parseable) — error returned
- Missing before or after field — defaults to empty object
- YAML or TOML input not supported — must be valid JSON

## How this service works

Change audit: DocFx Config (docfx.json): Audit JSON changes and validate before/after for DocFx Config (docfx.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 JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations, newly introduced errors, and errors that were resolved. Uses a pinned SchemaStore definition for DocFx Config validation.

## 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/docfx-config-docfx-json-change-audit-08314107/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)