# Change Audit for .omletrc

> Change Audit for .omletrc 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-15).

Audits JSON changes between two .omletrc documents, 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-omletrc-ae362a9d-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-for-omletrc-082bd54c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TSTCG-Pfqg8o-y-5j6p7Q

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-omletrc-082bd54c -d '<json body>'
```

Example prompt: Can you audit my .omletrc change — here's the before config and the after config — 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 need to specifically audit configuration changes to a .omletrc file, compare two versions for schema compliance using a pinned SchemaStore definition, or want a structured diff of JSON paths alongside introduced and resolved validation errors. Prefer this over generic JSON diff tools when .omletrc-specific schema validation matters.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Non-JSON input (YAML/TOML) provided — not parsed or validated
- Invalid JSON syntax in before or after field — parse error returned
- SchemaStore definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: .omletrc: Audit JSON changes and validate before/after for .omletrc. 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 .omletrc JSON documents including: JSON pointers for all added, removed, and changed paths; a list of schema rule violations introduced in the 'after' document; a list of errors resolved compared to the 'before' document; based on 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-omletrc-082bd54c/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)