# Change Audit: ODGS Data Rules

> Change Audit: ODGS Data Rules 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).

Audits JSON changes between two documents against the ODGS Data Rules schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-odgs-data-rules-97c199da-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-odgs-data-rules-d92d13cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i5B7Wc36BBDb8ubU6xW0W

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-odgs-data-rules-d92d13cb -d '<json body>'
```

Example prompt: Can you audit the changes I made to my ODGS Data Rules config? Here's the before version and after version — I want to know which JSON paths changed and whether I introduced or resolved any schema violations.

## When to prefer this

Use this endpoint when you specifically need to audit changes to ODGS Data Rules JSON documents and want both a structural diff (added/removed/changed paths) and a schema-compliance diff (introduced/resolved violations) in one call. Prefer it over generic JSON diff tools when ODGS Data Rules schema validation is required alongside the structural comparison.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting exceeds 32 levels — rejected with depth error
- Invalid JSON submitted (e.g. YAML or TOML) — parsing error returned
- Malformed request body — missing before or after field
- Payment not received — endpoint returns 402

## How this service works

Change audit: ODGS Data Rules: Audit JSON changes and validate before/after for ODGS Data Rules. 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 all JSON pointer paths that were added, removed, or changed between the before and after documents, plus any schema rule violations that were introduced or resolved, validated against a pinned SchemaStore definition for ODGS Data Rules.

## 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-odgs-data-rules-d92d13cb/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)